Skip to main content
Glama

get_product

Read-only

Get one Agent Field Kit product by id. Read-only.

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": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
      -  "cost-roi-calculator",
      -  "eval-test-plan",
      -  "incident-runbooks",
      -  "vendor-security-questionnaire",
      -  "afk-cyber-bundle-pro-year",
      -  "cyber-defense-bundle",
      -  "mcp-tool-access-review",
      -  "prompt-injection-test-pack",
      -  "agent-observability-starter",
      -  "agent-security-audit-kit",
      -  "realtime-agent-monitoring-kit",
      -  "ai-slop-editing-kit",
      -  "secrets-rotation-kit",
      -  "approval-gates-kit",
      -  "eu-ai-act-transparency-kit",
      -  "mcp-server-auth-kit",
      -  "agent-skill-authoring-kit",
      -  "ai-supply-chain-defense-kit",
      -  "inference-key-abuse-kit",
      -  "ci-registry-credential-kit",
      -  "oauth-grant-revocation-kit",
      -  "cyber-defense-dashboard-kit",
      -  "full-kit",
      -  "team-license"
      -]New value: +[
      +  "cost-roi-calculator",
      +  "eval-test-plan",
      +  "incident-runbooks",
      +  "vendor-security-questionnaire",
      +  "afk-cyber-bundle-pro-year",
      +  "cyber-defense-bundle",
      +  "mcp-tool-access-review",
      +  "prompt-injection-test-pack",
      +  "agent-observability-starter",
      +  "agent-security-audit-kit",
      +  "realtime-agent-monitoring-kit",
      +  "ai-slop-editing-kit",
      +  "secrets-rotation-kit",
      +  "approval-gates-kit",
      +  "eu-ai-act-transparency-kit",
      +  "mcp-server-auth-kit",
      +  "agent-skill-authoring-kit",
      +  "ai-supply-chain-defense-kit",
      +  "inference-key-abuse-kit",
      +  "ci-registry-credential-kit",
      +  "oauth-grant-revocation-kit",
      +  "cyber-defense-dashboard-kit",
      +  "agent-red-team-suite",
      +  "ai-spend-kill-switch-kit",
      +  "exposure-patch-alerts-kit",
      +  "full-kit",
      +  "team-license"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so 'Read-only' is a restatement rather than added context. The description says nothing about what happens with an invalid id, what the returned product contains, or whether results are cached — exactly the kind of detail annotations do not cover.

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?

Two short sentences, front-loaded with the action and resource, with no padding. The 'Read-only' clause is redundant with the annotation but costs little.

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?

With no output schema, the description should sketch what a product record contains, and it does not. For a simple one-parameter read tool it is adequate to enable a correct call, but an agent cannot anticipate the response shape or failure mode.

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?

There is a single parameter with 0% schema description coverage, but the enum enumerates every valid product slug, which is largely self-documenting. The description only confirms the id identifies a product and adds no format, casing, or lookup-miss guidance beyond the enum.

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 ('Get one Agent Field Kit product') and the lookup key ('by id'), so an agent can distinguish it from search_products or get_order without opening the schema. It stops short of naming a sibling, but the resource is unambiguous.

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?

The phrase 'by id' implies this is a single-record lookup as opposed to a listing/search, which gives some implicit routing guidance. There is no explicit statement of when to prefer search_products or what to do when the id is unknown, so usage is only implied.

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