Appearance
Research Sources
Agent Tool v0.2.0 uses established tool, API, eventing, telemetry, authorization, and agent protocol references. These references inform the shape of the standard; they do not transfer ownership of Agent Tool semantics.
| Source | What Agent Tool takes from it |
|---|---|
| Model Context Protocol tools specification | Tool discovery, tools/list, tools/call, name, title, description, inputSchema, outputSchema, content blocks, structuredContent, resource_link, embedded resources, annotations, isError, _meta, errors, and safety guidance. |
| Agent2Agent Protocol | Agent cards, skills, tasks, messages, artifacts, streaming events, auth scoping, native task/context/artifact ids, and peer-agent capability references. |
| OpenAI function calling guide | Function tools, tool calls, tool outputs, tool_call_id, tool choice, parallel tool calls, strict schema mode, custom tools, and tool search/deferred loading concepts. |
| OpenAPI Specification | Operation ids, methods, paths, request/response schemas, security schemes, and API operation mapping. |
| JSON Schema 2020-12 validation | Structural validation for input and output contracts. |
| OAuth 2.0 RFC 6749 | Authorization scopes, grants, tokens, and credential delegation references. |
| CloudEvents specification | Portable event envelope fields such as id, source, specversion, type, subject, time, and content metadata. |
| OpenTelemetry GenAI MCP conventions | Tool execution spans, tool names, arguments/results, JSON-RPC ids, MCP session ids, and trace/span correlation. |
| Agent Skills | AI-friendly authoring style, progressive disclosure, package-versus-runtime boundary, and skill/tool distinction. |
| in-toto Attestation | Signed statements and subject refs for tool-generated audit packages. |
Implementation analysis inputs
Agent Tool v0.2.0 also incorporates source-level analysis of coding-agent tool systems, especially their tool interfaces, permission flows, hook pipelines, streaming execution, tool search, file tools, shell tools, MCP adapters, and result persistence mechanisms. The public standard keeps the distilled contracts and avoids depending on any one product implementation.