Skip to main content
Glama

Ofr Search Funding Series

ofr_search_funding_series
Read-onlyIdempotent

Browse the full catalog of OFR repo-market and money-market-fund mnemonics by name (e.g. "tri-party", "GCF", "corporate debt", "federal reserve"), use this to find the exact series behind ofr_repo_rates/ofr_mmf_holdings, or a raw mnemonic to pass to ofr_funding_anomaly. OFR publishes no live search API, so this is a name/mnemonic lookup table, not a live call.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "tri-party"
    },
    "name": "ofr_search_funding_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 30, max 206 (the full catalog).
queryNoSubstring to match against the series name or mnemonic (case-insensitive). Omit to list everything in the chosen dataset.
datasetNoDefault all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, and the description adds genuinely new context: the catalog is static, not a live endpoint, and the full catalog size (206) is bounded. It does not describe the shape of a returned row (name vs mnemonic vs dataset), which is the remaining behavioral gap in the absence of an output schema.

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 dense sentence that front-loads the purpose before the routing guidance and the no-live-API caveat, with zero filler. The clause chaining into the sibling tool names is slightly run-on but still readable.

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

Completeness4/5

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

For a three-parameter, zero-required lookup tool with full schema coverage and annotations, the description covers purpose, consumers, and the static-data caveat. The only missing piece is what a match returns, which matters because no output schema is supplied.

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 query, dataset and limit are already documented, including the 206 maximum and the enum. The description adds only illustrative query values ('tri-party', 'GCF', 'corporate debt'), which is a modest supplement rather than new parameter semantics.

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 and resource ('Browse the full catalog of OFR repo-market and money-market-fund mnemonics by name') and immediately separates itself from ofr_repo_rates, ofr_mmf_holdings and ofr_funding_anomaly by naming them as consumers of its output.

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 routing: use it to find the exact series behind ofr_repo_rates/ofr_mmf_holdings, or to obtain a raw mnemonic to pass to ofr_funding_anomaly. It also excludes a false expectation up front by stating there is no live search API, so this is a lookup table rather than a live call.

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.