Skip to main content
Glama

Credit Guru

Search Credit Guru articles

search_articles
Read-onlyIdempotent

Search Credit Guru guides and news about credit cards, points and miles, bank bonuses and credit scores. Returns titles, summaries and links.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to search for, e.g. "balance transfer fee".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful information beyond that: the return payload shape (titles, summaries and links), which no output schema supplies. It omits any mention of the 20-result cap or ranking behavior.

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 sentences, no filler, with the domain scope front-loaded and the return format trailing. Every clause carries information an agent needs.

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 simple two-parameter search this is close to sufficient, and the return-value sentence compensates for the missing output schema. The undocumented limit parameter is the notable gap, since nothing tells an agent how to control result volume.

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

Parameters2/5

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

Schema coverage is only 50%: query is documented in the schema, but limit is not described in either place, and the description does not mention paging, result caps, or how to tune result count. The description contributes no parameter meaning at all, leaving half the input surface undocumented.

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 gives a specific verb ("Search") plus the resource and topical scope: Credit Guru guides and news covering credit cards, points/miles, bank bonuses and credit scores. That scope is enough to distinguish it from card-lookup siblings like get_card or find_cards, though it never names them.

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 implied by the topic list — an agent can infer this is for editorial/article content rather than card data — but there is no explicit when-to-use statement, no exclusion, and no pointer to an alternative tool.

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