Skip to main content
Glama
Sign In
Vibecoders MCP

Vibecoders MCP

by RaedBerjaoui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

load_tool

Fetch the complete input schema for a tool ID to learn its required parameters and make accurate calls.

Instructions

Get the full input schema for a qualified tool id (server.tool), so you can call it correctly.

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": {
      "id": "<id>"
    },
    "name": "load_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYese.g. playwright.browser_navigate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It reveals the behavior (fetching schema) but does not mention error handling, permissions, or what happens if the id is invalid. It is safe and read-only, but additional context would improve transparency.

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?

A single sentence that conveys the purpose and usage, with no wasted words. Packs essential information efficiently.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is complete enough: it states what it retrieves, the format expected, and the reason to use it. No significant gaps.

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

Parameters4/5

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

The schema covers the parameter with a description and example, and the tool description adds the 'qualified tool id (server.tool)' format requirement, which clarifies the expected structure beyond the schema's example. This adds meaningful semantics.

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?

Clearly states the verb 'Get' and the resource 'full input schema for a qualified tool id', which distinguishes it from siblings like call_tool (executes) and search_tools (finds tools). The 'server.tool' format is explicitly mentioned.

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?

Implies the tool is used when you need to call another tool correctly by first obtaining its schema. Does not explicitly state when not to use it or compare to alternatives, but the purpose is clear from the 'so you can call it correctly' phrasing.

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