AgentsJunction

Get MCP server

get_server

Use when you already know the exact name of an MCP server and need its full catalog record plus the versioned canonical resource profile.

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

Input Schema

Name	Required	Description	Default
`name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the return content (catalog record + versioned resource profile), which is useful since there is no output schema, and "get" implies a read. But it says nothing about auth requirements, rate limits, or what happens when the name does not exist.

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 is front-loaded with the usage condition and contains no filler. Every clause earns its place.

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

Completeness4/5

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

For a one-parameter read tool with no output schema and no annotations, the description covers the trigger condition and the returned payload well. The remaining gap is failure behavior (unknown name) and permission requirements, which are minor for this shape of tool.

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?

Schema coverage is 0% and the lone parameter has no description, so the description must compensate. "Exact name of an MCP server" establishes that the parameter is a server identifier and that exact matching is required, adding real meaning beyond the bare string/minLength schema.

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

Purpose4/5

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

States a specific verb (get) and resource (MCP server) and names what is retrieved: the full catalog record plus the versioned canonical resource profile. It implies the lookup-by-exact-name mode, which distinguishes it from the sibling search_servers, but never names that sibling explicitly.

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?

"Use when you already know the exact name" gives a clear triggering condition and implicitly excludes exploratory lookup (the job of search_servers). It stops short of naming the alternative tool or stating what to do when the name is unknown.

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

All AgentsJunction tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?