Skip to main content
Glama

Bancadia MCP

get_listing

Detail on 1-4 listings. Pick sections; detail_has shows what else exists. Features are capped; search_facts is better for text.

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": {
      "slugs": "<slugs>"
    },
    "name": "get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOnly features matching this text
slugsYes1-4 listing_slugs from list_business_checking
sectionsNosummary, tiers, fees, features, promotions. Default summary, tiers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It does reveal two useful traits: a hard cap on feature data and a 1-4 slug ceiling, but it omits permission/auth needs, what happens if more than 4 slugs are passed, whether truncation is silent, and the response shape. For an unannotated tool this leaves substantial behavioral gaps.

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, dense sentences with the scope constraint front-loaded and no filler. The middle sentence is slightly opaque ("detail_has shows what else exists") and costs a point for clarity rather than length.

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 3-parameter read tool with a fully documented schema and no output schema, this is close to adequate, but the dangling reference to detail_has and the unaddressed over-limit behavior leave an agent guessing at edge cases.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the 1-4 constraint on slugs, the need to actively choose sections, and the linkage between the capped feature set and the query parameter used to filter features. That is more than the schema states on its own.

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 concrete verb and resource ("Detail on 1-4 listings") and even carries the cardinality constraint, which meaningfully separates it from search_facts. It falls short of a 5 only because "Detail" is loose phrasing rather than naming the returned entity type (business checking listings).

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 routes text-oriented lookups to search_facts explicitly, which is real alternative guidance, and it advises picking sections. However, no when-not conditions are given, and the pointer "detail_has shows what else exists" is cryptic — it refers to a field the agent cannot confirm without calling another tool first.

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.