Skip to main content
Glama
Sign In

FXMacroData

by io.github.fxmacrodata
OverviewDiscussionsAdmin

Find FX Industry Organisations

organisation_search
Read-only

Find publication-cleared FX industry organisations by name or service, optionally within a business category. Returns at most ten directory references with canonical citation URLs; does not rank firms or export the database. Access: public directory references, no API key required.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum directory references, 1-10.
queryYesOrganisation name or service search, 2-120 characters, e.g. currency exchange.
categoryNoExact business category ID from directory results; omit to search all categories.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / properties / category / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / category / default
      Removed value: -null
    • addedInput schema / properties / category / description
      Added value: +"Exact business category ID from directory results; omit to search all categories."
    • addedInput schema / properties / category / type
      Added value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / limit / description
      Added value: +"Maximum directory references, 1-10."
    • addedInput schema / properties / query / description
      Added value: +"Organisation name or service search, 2-120 characters, e.g. currency exchange."
    • removedInput schema / title
      Removed value: -"organisation_searchArguments"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, openWorld and non-destructive semantics, yet the description adds real value: the ten-result ceiling, the fact that results carry canonical citation URLs, that firms are not ranked, and that access is public with no API key. That access and result-shape context is exactly what annotations cannot convey. Minor overlap with the schema's limit maximum is the only redundancy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly packed sentences: scope first, return shape second, access constraints third. Every clause carries information an agent would otherwise have to infer, and nothing is repeated.

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?

With an output schema present, return-value detail is not required, and the description still covers the essentials: matching keys, optional category narrowing, result cap, citation URLs, non-ranking behaviour and no-auth access. Nothing an agent needs in order to call this correctly 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%, so all three parameters are already documented, which sets the baseline at 3. The description reinforces meaning by framing 'query' as a name-or-service search and 'category' as an optional filter, and confirms the ten-result cap, but adds no syntax or format guidance beyond what the schema already states.

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 uses a specific verb ('Find') plus a well-defined resource ('publication-cleared FX industry organisations'), and states the matching keys (name or service, optional category). It implicitly separates itself from organisation_profile by emphasising that it returns 'directory references with canonical citation URLs' rather than profiles, but it never names that sibling explicitly.

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

Usage Guidelines4/5

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

It gives clear triggering context: look up organisations by name or service, optionally constrained to a business category. It also sets expectations (at most ten results, no ranking, no export), which steers the agent away from expecting bulk or ranked output. It stops short of naming a follow-up tool such as organisation_profile for detailed records.

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

All FXMacroData 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