PdfParse

Analysis Credit Memo

analysis.credit_memo

Read-onlyIdempotent

Generates a first-pass commercial loan credit memo with citations from already extracted rows, returning the memo in this call. Includes a crosscheck internally. Does not run or wait for extraction or save changes. Requires mcp:read and sends bounded row evidence to an external model: at most 80 rows from the first 200 matches, with long values shortened. Returns evidence coverage metadata and assumptions.

Input Schema

Name	Required	Description
`job_id`	No	Positive integer extraction job ID. Restricts rows to that job's document file IDs and must belong to table_id in the selected project. Omitting it adds no job restriction. This selects existing evidence; it does not start or wait for extraction.
`filters`	No	Row conditions combined with AND, also intersected with the job document restriction when job_id is supplied. An omitted or empty array adds no filtering. Each condition contains column, op, and value.
`table_id`	Yes	ID or slug of the table containing already extracted rows in the selected project. Required even with job_id; the job must belong to this table.
`memo_profile`	Yes	Required memo template identifier. The only supported value is commercial-loan-v1, for a first-pass commercial loan underwriting memo.
`project_slug`	No	Slug of an owned project. Optional only when the account has exactly one visible project; required for accounts with multiple visible projects.

Output Schema

Name	Required	Description	Default
`evidence`	No
`sections`	Yes
`risk_score`	Yes
`assumptions`	Yes
`memo_profile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 18, 2026

addedInput schema / properties / filters / description

Added value: +"Row conditions combined with AND, also intersected with the job document restriction when job_id is supplied. An omitted or empty array adds no filtering. Each condition contains column, op, and value."

addedInput schema / properties / filters / items / properties / column / description

Added value: +"Exact column name in the selected table, or document_record_id to select source file IDs. Unknown columns are rejected."

addedInput schema / properties / filters / items / properties / op / description

Added value: +"Comparison operator: eq/ne for equality/inequality, gt/gte/lt/lte for ordered comparisons, like for SQL patterns (% matches any sequence, _ one character), or in for membership."

addedInput schema / properties / filters / items / properties / value / description

Added value: +"Value matching the column type. Use a scalar for comparisons, a string pattern for like (for example Acme%), or an array for in (a scalar is also accepted as one item; an empty array matches no rows)."

addedInput schema / properties / job_id / description

Added value: +"Positive integer extraction job ID. Restricts rows to that job's document file IDs and must belong to table_id in the selected project. Omitting it adds no job restriction. This selects existing evidence; it does not start or wait for extraction."

addedInput schema / properties / memo_profile / description

Added value: +"Required memo template identifier. The only supported value is commercial-loan-v1, for a first-pass commercial loan underwriting memo."

addedInput schema / properties / project_slug / description

Added value: +"Slug of an owned project. Optional only when the account has exactly one visible project; required for accounts with multiple visible projects."

addedInput schema / properties / table_id / description

Added value: +"ID or slug of the table containing already extracted rows in the selected project. Required even with job_id; the job must belong to this table."

First observedOct 16, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds substantial context beyond them: it requires mcp:read, sends bounded row evidence to an external model (at most 80 rows from the first 200 matches, long values shortened), and returns evidence coverage metadata and assumptions. For an open-world tool that ships data to an external model, this disclosure is exactly the value-add.

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?

Purpose and the 'returns in this call' guarantee are front-loaded, and each subsequent sentence carries distinct information (internal crosscheck, no extraction/save, auth and data-bounding, return metadata). It is dense but not padded; four sentences for a tool with this much behavioral surface is efficient.

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?

An output schema exists, so return values need not be spelled out, yet the description still flags what matters operationally: in-call memo return, evidence coverage metadata, and assumptions. Combined with the auth requirement and external-model data limits, an agent has everything needed to call this correctly.

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 the schema already documents table_id, job_id, filters, memo_profile, and project_slug thoroughly, including job/table membership constraints. The description adds the bounded-row context but nothing per-parameter beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource ('Generates a first-pass commercial loan credit memo with citations from already extracted rows') and immediately clarifies the distinguishing boundary: it does not run or wait for extraction. Against the sibling analysis.crosscheck it also notes the crosscheck happens internally, so an agent can tell the two apart without opening either schema.

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 negative guidance ('Does not run or wait for extraction or save changes') and signals that crosschecking is internal rather than a separate call, which steers agents away from misuse. It stops short of naming a specific alternative tool or the conditions where a different tool would be preferred.

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

All PdfParse 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.