Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

Provides detailed credit score information for a specific organization using a tax code, VAT number

get_risk_IT_creditscore_top
Read-onlyIdempotent

Retrieve detailed credit score information for an Italian company by VAT or tax code to assess credit risk.

Instructions

Returns detailed credit score information for an Italian company.

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

Input Schema

NameRequiredDescriptionDefault
vat_or_taxCodeYesvatCode or taxCode of an italian company

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety and determinism profile is covered. The description adds 'detailed' and the Italian-only restriction, but says nothing about cost, rate limits, or what a call consumes — modest added value over structured fields.

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?

One front-loaded sentence with no filler or repetition. It is efficient, though it is arguably too thin to be considered exemplary structure for a financial-data tool.

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?

The tool is simple (one required string parameter, no output schema, annotations present), so the description needn't explain return values. However, for a credit-score lookup it gives no hint about score scale, coverage, or whether the identifier format matters, leaving the agent with a minimal picture.

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?

With a single parameter at 100% schema description coverage ('vatCode or taxCode of an italian company'), the schema carries the semantics. The description does not add format examples, validation rules, or whether VAT number and tax code are interchangeable for all entities, so baseline 3 applies.

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 specific verb and resource ('Returns detailed credit score information') and narrows the scope to an Italian company, which distinguishes it from the international siblings (get_company_WW_top, get_company_EU_advanced). It stops short of naming which sibling to use instead when a full company profile rather than a score is wanted.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as get_company_IT_advanced or get_company_IT_full. The only implied context is 'Italian company', which the agent must combine with sibling names to infer routing.

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