ca-rate-filings

Get Filing Source File Link

get_filing_source_file_link

Read-only

Returns a short-lived V4-signed GCS URL for a single SOURCE file (PDF / XLSM / XLSX / DOC / ZIP) the carrier submitted for a SERFF filing. The link is intended for display to the end user — they click it in their browser to download the file.

CRITICAL: DO NOT fetch this URL yourself. Surface it to the user verbatim and stop. The URL is a signed link for the human's browser, not for the model. Fetching it pulls the entire source file (often tens of MB of PDF / XLSM) into your context window and serves no purpose the user did not already get from seeing the link.

Pair with list_filing_source_files to discover the file names first, then call this to mint a link. When you respond to the user, include the URL and the expires_at timestamp so they know how long they have to click — after that the link returns 403 and they'll need to ask for a fresh one.

Link properties: direct V4-signed GCS URL, expires after ttl_seconds (default 900 = 15 min, capped at 3600). Bypasses Cloud Run entirely. Intended for human clicks, NOT for the model to fetch.

Whitelist is dynamic, keyed off the actual contents of the filing's source-files directory — same set list_filing_source_files advertises. file_name must be a basename (no slashes, no ..) AND must appear in the listing.

Returns { serff, file_name, url, expires_at, ttl_seconds, notice }. The notice repeats the don't-fetch directive — include it in your response to the user too.

Input Schema

TableJSON Schema

Name	Required	Description
`serff`	Yes	Canonical SERFF id, shape PREFIX-IDENTIFIER (e.g. "REGU-134742228").
`file_name`	Yes	Basename of a file present in this SERFF's source-files directory (the exact set returned by `list_filing_source_files`). No slashes, no path traversal — pure basename.
`ttl_seconds`	No	Signed-URL lifetime in seconds. Default 900 (15 minutes). Capped at 3600 (1 hour). Shorter is preferred — the link is for the human to click immediately, not for long-term storage.

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=true), describes link expiry, bypassing Cloud Run, dynamic whitelist, and return fields including a notice. No contradictions; adds substantial behavioral context.

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?

Well-structured with bold directives and separate paragraphs. Slightly verbose but each sentence adds necessary context. Front-loaded with critical don't-fetch instruction.

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?

No output schema, but description lists all return fields and explains error condition (403 after expiry). With 3 params fully covered and clear workflow pairing, it is complete for a URL-minting 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 covers all 3 params (100%). Description adds value by clarifying file_name must be a basename from the listing and ttl_seconds defaults/caps. Does not merely repeat 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 explicitly states the tool returns a short-lived V4-signed GCS URL for a single source file (PDF/XLSM etc.) and distinguishes it from the sibling 'list_filing_source_files' by noting the workflow: discover files first, then call this.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'CRITICAL: DO NOT fetch this URL yourself' directive and explains pairing with list_filing_source_files. Also advises including the expires_at timestamp so the user knows the link's validity period.

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

All ca-rate-filings tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation4/5

The get_filing_* family has distinct purposes, though get_filing_lineage and get_filing_references could be confused without the detailed descriptions. The search_* tools are clearly separated by embedding surface, and dossier/composite vs single-filing retrievals are explicitly differentiated.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern with clear prefixes: get_filing_*, search_*, list_*, and mcp_*. No style mixing or vague generic verbs.

Tool Count4/5

At 16 tools, this sits at the upper edge of the ideal range. Each tool earns its place, though get_filing_dossier could have been a client-side composition of the other get_filing_* calls rather than a separate tool.

Completeness5/5

The domain (retrieving CA rate filings) is covered end to end: structured and semantic search across multiple granularities, filing summaries, correspondence threads, actuarial numerics, lineage, source file listing/download, and reviewer caseload. The read-only nature of the domain means no create/update operations are needed, and every retrieval path leads to a terminal artifact.

Resources

Need Help?