Skip to main content
Glama

Credit Guru

List current offers

list_current_offers
Read-onlyIdempotent

Bank account bonuses and card welcome offers Credit Guru checked in the last 30 days: reward, requirements, fees, deadline, the catch and the official source.

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

Input Schema

NameRequiredDescriptionDefault
kindNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context — and it does: it discloses data provenance ('Credit Guru checked'), a freshness window of 30 days, and that each offer carries requirements, fees, deadline, caveats and an official source link. It does not say how many offers come back, whether results are ordered, or what an empty result looks like.

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?

A single sentence that front-loads the resource and freshness window, then lists the payload fields. There is no filler or repetition. The only structural weakness is that it is a noun phrase with no verb, so the action ('list') must be inferred from the tool name.

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 one-optional-parameter read tool with no output schema, the description does a reasonable job of describing the returned fields, which substitutes for the missing output schema. However, it leaves the sole parameter undocumented and says nothing about result volume or ordering, which an agent would want before calling. Adequate but with clear gaps.

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 description coverage is 0% and the description never mentions the single `kind` parameter. The enum values (bank, personal-card, business-card, education) are self-explanatory, but the description does not say what happens when `kind` is omitted — whether all categories are returned or the call fails. With zero coverage, the description was the only place to compensate and it does not.

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 names a concrete resource — bank account bonuses and card welcome offers verified in the last 30 days — and enumerates the fields returned (reward, requirements, fees, deadline, the catch, official source). That is far more specific than the name alone. It stops short of distinguishing itself from siblings like find_cards or get_best_cards, so an agent must infer that this one returns curated/verified offer listings rather than search results.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The only scoping signal is the implicit 'checked in the last 30 days' freshness window, which is a data constraint rather than a routing rule. An agent has to guess whether this or find_cards is the right entry point for a card-shopping query.

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