Skip to main content
Glama

check_integration

Read-only

Answer "does HelloBooks work with <bank/app/service>?" deterministically. Pass a name (e.g. "Stripe", "HDFC Bank", "Shopify", "QuickBooks"). Returns a supported yes/no with the matched integration and its rollout status (live/beta/coming-soon), or the closest catalog suggestions when there is no direct match. Prefer this over free-text search when the user names a specific provider.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe bank, payment provider, app, or service to check, e.g. "Stripe", "HDFC Bank", "Shopify", "QuickBooks".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description goes further by disclosing the return contract, including the live/beta/coming-soon status values and the suggestions fallback for non-matches. It stops short of explaining matching rules (exact vs. fuzzy, case sensitivity) or failure behavior for an empty query, which would make the deterministic-matching claim fully auditable.

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?

The purpose is front-loaded and the sentences are short and functional. The only slight waste is re-listing the example provider names that the input schema already supplies.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with no output schema, the description covers everything an agent needs: what to pass, what comes back in both match and no-match cases, and when to choose it over a sibling. Nothing material is missing.

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 100%, and the parameter already documents itself with the same examples (Stripe, HDFC Bank, Shopify, QuickBooks) that appear in the description. The description adds only the framing that `name` can be a bank, payment provider, app, or service, so the schema is doing the heavy lifting — baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise function: answering whether HelloBooks integrates with a named provider, and it spells out the return shape (a `supported` flag, matched integration with rollout `status`, or catalog `suggestions`). This distinguishes it cleanly from catalog-listing siblings like list_integrations and from free-text search.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: use this when the user names a specific provider, and prefer it over free-text search. That is a concrete when-to-use condition plus a named alternative, leaving nothing to infer.

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