Skip to main content
Glama

Origen Capital

What the directory covers

origen_financing_coverage

Coverage of the Origen Capital directory. Without arguments: national totals, per-lane counts, sources with vintages and refresh cycles. With a state: its county coverage and largest county lists, so an agent can form a valid lookup.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "origen_financing_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoUS state name or two-letter code (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the returned content in both invocation modes, including per-lane counts, source vintages, and refresh cycles. It does not explicitly state that the operation is read-only or describe output formatting, but the coverage-oriented framing makes the read semantics clear.

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?

The definition is two tight sentences with no wasted wording. It front-loads the overall purpose and then immediately explains the two invocation modes and their outputs.

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 low-complexity discovery tool with one optional parameter and no output schema, the description is nearly complete: it explains what each mode returns and why an agent would use it. The only gap is a lack of explicit read-only or output-format context, which is minor here.

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 schema already documents the single optional 'state' parameter. The description adds meaningful semantics beyond the schema by explaining that supplying a state changes the result from national totals to county coverage and largest county lists.

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 the tool reports directory coverage for Origen Capital and clarifies the two modes: national totals and lane/source details without arguments, or county coverage for a specific state. It implicitly distinguishes itself from the lookup tool by saying the result lets an agent 'form a valid lookup,' though it does not name siblings 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 usage conditions for both modes: call without arguments for national totals and source metadata, or pass a state for county coverage and largest county lists. The phrase 'so an agent can form a valid lookup' provides a practical reason to call it before lookup operations, but it does not explicitly state when not to use the tool or name alternatives.

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