Skip to main content
Glama
Sign In

Global FinReg

by com.globalfinreg
OverviewDiscussionsAdmin

Get renewal price

get_renewal_quote
Read-onlyIdempotent

Returns the price of renewing one of the user's LEIs for 1, 3 or 5 years: net amount, VAT, total and currency, the renewal year and order id, the payment methods (card, invoice) and any unpaid renewal order the user already started. The price is in the account's currency: if the user hasn't said which currency they want to pay in, ask them first and change it with set_currency. If vatNote says VAT could be taken off, ask the user for the entity's EU VAT number and pass vatCountry and vatNumber. Always show the user this price and get their agreement before calling create_renewal_order.

Input Schema

NameRequiredDescriptionDefault
leiIdYesThe id (GUID) of the LEI, from list_my_leis or list_leis_due_for_renewal.
yearsNoRenewal period in years: 1, 3 or 5. Longer periods have a lower price per year.
vatNumberNoOptional: the entity's EU VAT number, e.g. BE0123456789. It is checked with the EU's VIES service, and only a valid number is used. Pass the same vatCountry and vatNumber to the order tool as to the quote.
vatCountryNoOptional: the 2-letter code of the EU country that issued the entity's VAT number, e.g. BE. Give it with vatNumber when the quote adds VAT and the entity has an EU VAT number; leave both out to use the VAT number already stored for this LEI.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / vatCountry
      Added value: +{
+  "default": null,
+  "description": "Optional: the 2-letter code of the EU country that issued the entity's VAT number, e.g. BE. Give it with vatNumber when the quote adds VAT and the entity has an EU VAT number; leave both out to use the VAT number already stored for this LEI.",
+  "type": "string"
+}
    • addedInput schema / properties / vatNumber
      Added value: +{
+  "default": null,
+  "description": "Optional: the entity's EU VAT number, e.g. BE0123456789. It is checked with the EU's VIES service, and only a valid number is used. Pass the same vatCountry and vatNumber to the order tool as to the quote.",
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description stays consistent while adding context the annotations cannot: the exact price breakdown returned, the presence of payment methods, and that any already-started unpaid renewal order is surfaced. It does not discuss pagination, error cases, or what happens to a stale quote, so it falls short of a 5.

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?

Dense but front-loaded: what it returns comes first, then the currency prerequisite, then the VAT branch, then the confirmation requirement before ordering. Every sentence carries an instruction, though the single long paragraph could be split into steps for faster scanning.

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 read-only quote tool with no output schema, the description supplies the return shape, the currency prerequisite, the VAT-number branch, and the hand-off to create_renewal_order. An agent has everything needed to call it and act on the result without further discovery.

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 semantics beyond the schema: it explains the conditional trigger for vatCountry/vatNumber (vatNote says VAT may come off) and the cross-tool rule that the same VAT pair must be passed to the order tool. The leiId source is only documented in the schema, not the description.

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?

States a specific verb+resource ('Returns the price of renewing one of the user's LEIs') with scope (1, 3 or 5 years) and enumerates the returned fields. It is clearly distinguishable from get_prices, get_registration_quote and get_renewal_order without opening any schema.

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?

Gives explicit preconditions and routing: if currency is unspecified, ask the user and call set_currency; if vatNote indicates VAT is removable, collect the EU VAT number and pass vatCountry/vatNumber. It also names the downstream tool (create_renewal_order) and states the required user agreement step before calling it.

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

All Global FinReg toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources