Skip to main content

Tool Call Formats

ValorIDE uses a simple structured format when invoking tools (MCP servers, local helpers, or shell commands). This doc explains the shapes and best practices for tool calls so authors and integrators can write compatible tools.

Basic pattern​

  • Tool name: string identifier (e.g. mcp:github, skill:testing)
  • Input: JSON object with typed fields
  • Output: JSON object or rich content (images, HTML previews) depending on tool

Example:

{
  "tool": "mcp:gitlab",
  "input": { "repo": "org/repo", "sha": "abc123" }
}

Best practices​

  • Keep inputs small and explicit
  • Prefer JSON schemas for tool inputs
  • Provide rich, helpful error objects (code + message + remediation)

Verification​

Tools should return deterministic results for given inputs and provide an idempotency key when applicable.