PersonIQ

Download a person report as Markdown

export_report_markdown

Read-only

Save a person report as a downloadable .md file and return a link. FREE — it is the same document format: "report" already returns, delivered as a file rather than inline, for saving or filing. Use the inline report when the user just wants to read it; use this when they want to keep it. The link expires after one hour; re-exporting within that window returns the same file and is also free.

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": {
      "searchId": "<searchId>",
      "personId": "<personId>"
    },
    "name": "export_report_markdown"
  }
}

Input Schema

Name	Required	Description
`format`	No	Rendering of the human-readable text channel. "prose" (default) is a compact summary an agent can reason over; "json" repeats the data verbatim; "report" is a formatted Markdown report to show a person; "html" is a standalone HTML document for saving, printing or PDF. Machine-readable structuredContent is always included either way.
`personId`	Yes	personId of the subject to export.
`searchId`	Yes	searchId returned by search_person.
`idempotencyKey`	No	Optional. Pass the same value when retrying a call that may have already succeeded, and you will not be charged twice.

Output Schema

Name	Required	Description	Default
`reused`	Yes
`fileName`	Yes
`mimeType`	Yes
`expiresAt`	Yes
`sizeBytes`	Yes
`downloadUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations (which only establish it is a safe read), the description discloses cost (free, not charged), link lifetime (one hour), and caching behavior (re-export within the window returns the same file at no cost). It also clarifies the content is identical to the inline report, so the agent knows nothing new is generated. These are exactly the behavioral facts an agent cannot get from annotations or 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?

The action and result are front-loaded in the first clause, then use case, then cost/lifetime caveats in descending priority. Minor redundancy between "FREE" and the later "also free," but no sentence is wasted.

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?

With annotations covering safety, an output schema covering return values, and full param documentation, the description fills the remaining gaps: cost, expiry, caching, and the read-vs-keep decision. The only omission is routing to the PDF sibling, which matters for an export-format tool.

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 description coverage is 100%, so the baseline is 3, and the description adds cross-parameter meaning by explaining that this tool's output is the same document that format:"report" returns. It adds little about searchId or personId, but the schema already covers those adequately.

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 ("Save a person report as a downloadable .md file and return a link") and ties it to the format:"report" rendering, so the agent knows exactly what artifact is produced. It does not name the sibling export_report_pdf, so the file-format choice among siblings is only inferable from the ".md" wording.

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 an explicit when/when-not pair: "Use the inline report when the user just wants to read it; use this when they want to keep it." That resolves the main decision the agent faces. The remaining alternative, exporting to PDF, is never mentioned despite export_report_pdf being a sibling.

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

All PersonIQ 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?