FinFam Financial Calculators

get_pulse

Read-onlyIdempotent

Get the current FinFam Pulse — FinFam's twice-daily money-news digest.

    Use this for "what's happening in finance / markets / the economy right now"
    questions instead of answering from memory. Returns a dated headline and
    paragraph, the overall mood, a finfam.app permalink, the external grounding
    sources, and the edition's story cards (each with its own article URL). Cite
    the permalink and the story URLs. Returns null when nothing is published yet.

    Args:
        period: 'today' for the latest daily read, 'week' for the running weekly read

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No		today

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it returns null when nothing is published yet, which is useful behavioral context beyond the annotations. It also details the return structure (headline, mood, permalink, sources, story cards), which is helpful.

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?

The description is well-structured with a clear first sentence, then usage guidance, return details, and parameter explanation. It is concise and front-loaded with the core purpose, with no wasted words.

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?

Given the tool's simplicity (one optional parameter, no nested objects), the description covers purpose, usage, return values, and edge case (null). The output schema exists, so return details are reinforced. The description is complete for an agent to select and invoke correctly.

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 schema has only one parameter with a default, and the description explains the two allowed values ('today' and 'week') and their meanings. Since schema coverage is 0%, the description fully compensates by defining the parameter semantics clearly.

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 clearly states the tool retrieves the current FinFam Pulse, a twice-daily money-news digest, and explicitly contrasts it with answering from memory. It distinguishes from siblings like search_pulse by focusing on the current digest rather than searching historical ones.

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?

The description explicitly says to use this for 'what's happening in finance / markets / the economy right now' questions instead of answering from memory, and it mentions the period argument for today vs week. It also instructs to cite the permalink and story URLs, providing clear usage guidance.

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

All FinFam Financial Calculators 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.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose. The calculator tools cover search, contract, source, and execution, while the pulse tools cover current retrieval and search. No two tools overlap in function, so an agent can reliably select the correct one.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: calculate_view, get_pulse, get_view_signature, get_view_source, search_pulse, search_views. The verbs and nouns are clear, and the naming scheme is uniform across the set.

Tool Count5/5

Six tools is well within the ideal range for a focused server. Each tool addresses a distinct need within the financial calculator and news digest scope, making the count feel neither bloated nor sparse.

Completeness4/5

The calculator lifecycle is well covered: find a view, understand its inputs, optionally inspect its source, and run it. The pulse feature also covers current retrieval and historical search. A minor gap is the absence of a direct 'get view' operation independent of search, but this is workable via search_views.

Resources

Need Help?