Skip to main content
Glama

search_card_terms

Read-only

Search the web for a credit card's published reward terms and return raw snippets to summarize and confirm before saving.

Instructions

Search the web for a card's published reward terms. Results are raw snippets: summarise them for the user and confirm before saving anything.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat to look forreward rate cashback cap
card_nameYese.g. 'HDFC Millennia'
max_resultsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and open-world scope (openWorldHint=true). The description adds genuinely new behavioral information: results are unstructured raw snippets, and saving anything derived from them requires user confirmation. That materially shapes how the agent should handle the output. It does not mention result reliability or failure modes for empty searches, keeping 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.

Conciseness5/5

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

Two short sentences, front-loaded with the purpose, followed by a single actionable handling instruction. Nothing is redundant and every clause adds information the agent does not get from structured fields.

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?

An output schema exists, so return values needn't be explained, yet the description still characterizes the return as raw snippets, which is useful framing. For a read-only, annotated, three-parameter search tool this is nearly complete; only the lack of explicit routing versus sibling tools and the undocumented max_results leave a gap.

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 67%, with topic and card_name documented in-schema (including an example) while max_results has no description. The tool description says nothing about any parameter's meaning, format, or tuning. With coverage in the mid range, the schema does most of the work and a baseline 3 is appropriate.

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 and resource: 'Search the web for a card's published reward terms.' The scope ('published reward terms', i.e. external web content) is clearer than a bare 'search'. It doesn't explicitly distinguish itself from a sibling like card_details, which presumably reads stored card data, so it stops short of a 5.

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?

Usage is only implied: the agent can infer this is for looking up external, published terms rather than stored card data. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for cases where the answer is already available locally. The closing instruction ('summarise them for the user and confirm before saving anything') is workflow guidance rather than tool selection guidance.

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