Skip to main content
Glama

Worthune Verified Financial Models

by com.worthune
OverviewDiscussionsAdmin

get_model_contract

Read-onlyIdempotent

Get a model's machine-readable contract: required inputs with types and valid domains, cross-field constraints, sentinel-value meanings, and the government constants (with sources) the model uses. Set include_spec to also receive the full specification markdown (exact formulas, assumptions, exclusions, known issues).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesModel name from list_models, e.g. 'relocation'
api_keyNoWorthune API key (wk_…) — required for include_spec on non-sample models; or send it once as an Authorization: Bearer header.
include_specNoAlso return the full spec markdown (default false). Public for the free-sample models; other models need api_key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Worthune Pro API key (wk_…) — required for include_spec on non-sample models."New value: +"Worthune API key (wk_…) — required for include_spec on non-sample models; or send it once as an Authorization: Bearer header."
  2. Changed2 schema fields changed
    • addedInput schema / properties / api_key
      Added value: +{
+  "description": "Worthune Pro API key (wk_…) — required for include_spec on non-sample models.",
+  "type": "string"
+}
    • changedInput schema / properties / include_spec / description
      Previous value: -"Also return the full spec markdown (default false)"New value: +"Also return the full spec markdown (default false). Public for the free-sample models; other models need api_key."
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds substantive behavioral context by explaining the conditional output when include_spec is set and the machine-readable content returned, which is valuable beyond the structured fields.

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 tight sentences with front-loaded purpose. The first sentence states exactly what the tool returns, and the second adds the optional behavior without any filler or repetition of schema details.

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?

The description gives a clear picture of the return value even without an output schema, enumerating the contract sections and the optional markdown spec. Combined with the detailed parameter schema and safety annotations, everything an agent needs to call the tool correctly is present.

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 model, api_key, and include_spec in detail. The description mostly explains the return content rather than adding new parameter-level meaning, so it does not need to compensate for missing schema information. Baseline 3 is appropriate.

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: 'Get a model's machine-readable contract'. It then enumerates what the contract contains (required inputs, types, valid domains, cross-field constraints, sentinel values, government constants), making the tool's purpose concrete and distinct from sibling listing tools like list_models.

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

Usage Guidelines3/5

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

The description makes the intended use clear—fetching a contract or adding the full specification via include_spec—but it never explicitly names alternative tools or states when not to use this one. It indirectly references list_models in the schema for the model parameter, but the description itself does not provide exclusion or routing guidance.

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

All Worthune Verified Financial Models toolsInspect
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