Skip to main content
Glama

Get Zicron's medical chronology offer

get_offer
Read-onlyIdempotent

Returns Zicron's done-for-you medical chronology service: what is delivered (case summary plus an all-provider timeline with a page citation on every entry), who it is for (plaintiff PI, med-mal and nursing-home firms, and legal nurse consultants), the published price per case and per page, first-case discount and refund guarantee, the wholesale offer for LNCs, 48-hour turnaround, scope limits (medical facts only; no standard-of-care, causation or damages opinions), security practices and how to start. Use this when a user asks what Zicron does, what a chronology from Zicron includes, or whether it fits their case. Read-only; no side effects. If the user already has records and a Zicron account, tell them to connect https://claims.zicron.ai/agent/mcp (OAuth) instead of requesting a chronology here.

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": "get_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
forNoWho the service is for.
urlsNoPages for humans.
errorNoPresent only when isError is true: why the call was refused and what to do next.
priceNoPublished price: per_case, included_pages, per_page_over_included, first_case_discount_percent, examples.
scopeNoWhat is included and excluded (no standard-of-care, causation or damages opinions).
serviceNoThe service offered.
summaryNoWhat is delivered.
providerNoWho provides the service and how to reach them.
securityNoSecurity practices.
correctionsNoCorrection policy.
deliverablesNoWhat the chronology contains.
how_to_startNoSteps to start a case.
honesty_notesNoLimits to state plainly to the user.
offer_versionNoPrice list version.
records_policyNoWhere records may and may not be sent.
for_lnc_partnersNoWholesale offer for legal nurse consultants.
turnaround_hoursNoTurnaround in hours.
turnaround_startsNoWhen the turnaround clock starts.
first_case_guaranteeNoThe first-case refund guarantee.
first_case_refund_window_daysNoDays to ask for the first-case refund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation behavior: scope limits (medical facts only, no standard-of-care/causation/damages opinions) and the redirect to the OAuth endpoint. It does not describe rate limits or caching, but those are minor for a read-only offer tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The middle sentence is a dense, comma-heavy enumeration of service attributes (deliverables, audience, pricing, discount, wholesale, turnaround, scope, security, onboarding) that packs a lot into one breath. It is front-loaded and information-rich, but it reads more like a marketing spec sheet than a tight tool description and could be structured with clearer segmentation.

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 an output schema present, the description needn't document return values, and annotations cover the safety semantics. It covers audience, scope, pricing, and the funnel step, giving the agent enough to decide whether to call it. A slight gap remains: it does not hint at how the returned offer payload is structured versus quote_chronology's numerical output.

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?

The tool has zero parameters, which is the documented baseline of 4. The description correctly implies a no-argument info fetch and adds no misleading parameter claims.

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 specifies the exact resource (Zicron's done-for-you medical chronology service) and enumerates its contents, pricing, turnaround, and scope. It is immediately distinguishable from siblings like get_sample_chronology, quote_chronology, and request_chronology, each of which covers a different step in the funnel.

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?

It states explicit when-to-use triggers ('what Zicron does, what a chronology includes, or whether it fits their case') and a clear exclusion with a named alternative endpoint (connect the OAuth MCP if the user already has records and an account). That is the strongest possible routing guidance.

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