Zeitro: Mortgage Guidelines

Read agency guideline pages

get_document_pages

Read-onlyIdempotent

Returns the full text of up to 5 consecutive pages of one agency guideline document (Fannie Mae, Freddie Mac, FHA, VA or USDA), with the document, version date, a ready-made citation and links. Useful when a passage is cut off or a table continues onto the next page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "doc_id": "<doc_id>",
      "start_page": "<start_page>"
    },
    "name": "get_document_pages"
  }
}

Input Schema

Name	Required	Description
`doc_id`	Yes	doc_id of an agency guideline document, from search results or the document list.
`end_page`	No	Last page to read (inclusive). Defaults to start_page. At most 5 pages per call.
`start_page`	Yes	First page to read, 1-based.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is to add shape to the result. It does: callers learn the response carries the text, the document identity, a version date, a ready-made citation, and links, plus the 5-page-per-call ceiling. It omits any note on out-of-range pages or invalid doc_id handling.

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?

Two sentences, zero filler, with the core capability stated first and the trigger condition second. The parenthetical agency list is the only bulk, and it earns its place by defining the valid source universe.

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?

Rich annotations and a full output schema mean the description needn't explain safety or return shape, and it still summarizes the payload helpfully. For a simple three-parameter range reader, nothing an agent needs to invoke it correctly is absent.

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?

With 100% schema coverage the baseline is 3, and the description adds two things the schema does not: the set of agencies a doc_id can refer to, and the 'consecutive pages' constraint tying start_page and end_page together. It still does not restate the 1-based nature or default behavior of end_page, leaving that to the schema.

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?

The description opens with a specific verb and resource: 'Returns the full text of up to 5 consecutive pages of one agency guideline document,' and enumerates the covered agencies (Fannie Mae, Freddie Mac, FHA, VA, USDA). The page-range scope and single-document-by-doc_id framing make it plainly distinct from a keyword search tool like search_guidelines.

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 a concrete when-to-use condition: 'Useful when a passage is cut off or a table continues onto the next page,' which tells the agent to follow up after a truncated excerpt. It does not state when not to use it or name an alternative (e.g. go back to search_guidelines when no doc_id is known), so it stops short of full routing guidance.

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

All Zeitro: Mortgage Guidelines tools Inspect

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

Need Help?