# inspect_tool

> Full description and JSON input schema of one tool.

URL: https://mcp-docs.opennomos.com/docs/tools/discovery/inspect_tool

> Full description and JSON input schema of one tool.

| Field | Value |
| --- | --- |
| Pack | Core (`core`) |
| Estimated cost per call | $0 |
| Monthly pack limit | none |
| Project | resolved: explicit `project` → header → credential default → workspace default |

## Parameters

| Parameter | Required | Type | Description |
| --- | --- | --- | --- |
| `name` | yes | `string` | Tool name, e.g. 'seo_research'. |

## Example call

```json
{
  "name": "seo_research"
}
```

REST: `POST https://service.opennomos.com/v1/tools/inspect_tool` with that JSON as the body. MCP: `tools/call` with `name: "inspect_tool"` and that JSON as `arguments`.

## Example result

Values are illustrative; the shape comes from the service code.

```json
{
  "name": "seo_research",
  "description": "SEO data. action=serp: …",
  "inputSchema": {
    "type": "object",
    "properties": "…",
    "required": [
      "action"
    ]
  }
}
```

## Notes

- Returns the same `name`, `description` and JSON Schema that `tools/list` (MCP) and `GET /v1/tools` publish.
- An unknown tool, or one whose pack is not enabled, returns the error `No tool <name>`.

## Errors

Rejected calls (bad input, unknown ids, rate limits) return `message` and `code`; over MCP the result has `isError: true`. See [Errors](https://mcp-docs.opennomos.com/docs/reference/errors.md).