Skip to main content
Glama

Calder Vale Supply Inventory

partner_accounts

Read-only

Account managers only. Returns partner contacts and credit terms. Public client access does not authorize it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "partner_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
partnerNoPartner name or account number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds meaningful context beyond that by disclosing an authorization requirement and by naming the returned content (contacts and credit terms) in the absence of an output schema. It does not mention pagination or result size, which keeps it from a 5.

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

Conciseness4/5

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

Three short, waste-free sentences. The access restriction is front-loaded and the purpose follows immediately, though leading with eligibility rather than the function slightly delays the core statement.

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

Completeness3/5

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

For a single-parameter read tool this covers purpose, eligibility, and returned fields. The gap is the unaddressed default case — with zero required parameters, an agent cannot tell from the description whether omitting 'partner' lists all partner accounts or is invalid behavior.

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% for the single 'partner' property, so the schema already explains the parameter and the baseline of 3 applies. The description adds no format or matching details, and notably does not say what happens when the optional 'partner' argument is omitted.

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?

The description states a specific verb and resource — 'Returns partner contacts and credit terms' — which is concrete enough to distinguish it from the sibling inventory/order/price tools without opening the schema. It stops short of naming an alternative tool, so it is clear but not fully sibling-differentiated.

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

Usage Guidelines3/5

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

It specifies who may call it ('Account managers only' and 'Public client access does not authorize it'), which is a real eligibility constraint, but it gives no guidance on when to prefer this tool over a sibling or what situation calls for it. Usage is implied by role rather than explained.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources