Skip to main content
Glama

Origen Capital

Look up one institution

origen_institution

Find an institution in the directory by name (optionally narrowed to a state) or by the id a lookup returned. Returns its kind, certifications, lanes, head-office county, every county where it keeps a door, and the federal list and vintage it comes from. Answers 'not in the directory' plainly — most banks are not in it by design.

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_institution"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAn id from a previous lookup, e.g. 'california/mission-asset-fund-cdfi' (optional; overrides name)
nameNoInstitution name or part of it, e.g. 'Mission Asset Fund'
stateNoUS state name or two-letter code (optional)
languageNoLanguage for notes, default 'en'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose key behavior: the exact returned fields (kind, certifications, lanes, head-office county, all counties with a door, source federal list and vintage) and the plain negative-result behavior. The coverage caveat that most banks are absent by design is a valuable non-obvious trait. It never explicitly states this is a read-only operation or what error/permission conditions look like.

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?

Three tight sentences, front-loaded with the lookup modes before the return payload and the coverage caveat. The return-field list is long but earns its place because there is no output schema.

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?

Return values are described in detail, which is necessary given no output schema, and the directory-coverage caveat is included. The significant remaining gap is that with zero required parameters the description never says what an empty invocation does — enumerate the directory, or fail — which an agent needs in order to call it safely.

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 coverage is 100%, so the baseline is 3; the description adds little beyond the schema, which already documents the id-overrides-name precedence and the state narrowing. Notably, all four parameters are optional, and neither the schema nor the description explains what a call with no arguments returns.

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?

States a specific verb and resource ('Find an institution in the directory') and spells out the two lookup keys — name (optionally with state) or a previously returned id. It does not name or contrast any of the sibling financing tools, so the agent must infer the boundary between this directory lookup and origen_financing_lookup.

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?

Gives clear usage context: look up by name, optionally narrowed to a state, or by an id from a previous lookup. The sentence about answering 'not in the directory' plainly and most banks not being included 'by design' tells the agent when a negative result is expected rather than an error. No explicit alternative tool is named.

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