Skip to main content
Glama
Sign In
MCPNexus

MCPNexus

by KrzysztofAugiewicz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mcpd_get_schema

Read-only

Retrieve the full input schema for a specific tool from a connected MCP server. Use after lazy connect to avoid loading all schemas at once.

Instructions

Get full inputSchema for ONE tool from a server. Use after mcpd_connect(lazy_mode=true) to avoid loading all schemas at once. Returns the schema needed to call the tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server_id": "<server_id>",
      "tool_name": "<tool_name>"
    },
    "name": "mcpd_get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
server_idYesServer ID (e.g. github)
tool_nameYesTool name (e.g. create_issue)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=true and openWorldHint=false. The description adds useful behavioral context by explaining the lazy loading pattern and that the tool returns the schema needed to call the tool. It does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long and front-loaded: the first sentence states the core purpose, the second adds usage context. Every sentence is essential and there is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with 2 parameters and no output schema, the description provides sufficient context: it explains the purpose, usage in the lazy workflow, and what is returned ('the schema needed to call the tool'). It is complete without needing additional details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already fully documents both parameters. The description adds no additional meaning beyond what is in the schema. Baseline is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Get full inputSchema for ONE tool from a server', using a specific verb and clear resource. It differentiates from sibling tools (mcpd_find, mcpd_list, mcpd_connect) by specifying that it retrieves a single schema, not a list or connection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage guidance: 'Use after mcpd_connect(lazy_mode=true) to avoid loading all schemas at once.' It clearly indicates when to use this tool, though it does not explicitly mention when not to use it or provide direct alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools