day_count_fraction

Exact day-count fraction between two dates under a market convention. Dates are ISO YYYY-MM-DD. For ACT/ACT ICMA also pass frequency (coupons per year) and, for stub periods, the reference period boundaries. Deterministic; do not estimate this with a model.

Server Shikamaru JayOfemi/shikamaru
Category Read
Risk class Low
Parameters 00 required

What day_count_fraction does on Shikamaru

AI agents call day_count_fraction to retrieve information from Shikamaru without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why day_count_fraction needs a policy

This is a pure computational read operation. It takes date inputs and conventions as parameters and deterministically returns a calculated day-count fraction—a numeric query result with no side effects. There is no data creation, modification, deletion, code execution, or financial transaction.

From the tool's definition Tool computes and returns 'exact day-count fraction between two dates under a market convention' with no modification, deletion, creation, or execution of external operations.

Questions about day_count_fraction

What does the day_count_fraction tool do? +

Exact day-count fraction between two dates under a market convention. Dates are ISO YYYY-MM-DD. For ACT/ACT ICMA also pass frequency (coupons per year) and, for stub periods, the reference period boundaries. Deterministic; do not estimate this with a model. It is categorised as a Read tool in the Shikamaru MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on day_count_fraction? +

Register the Shikamaru MCP server in PolicyLayer and add a rule for day_count_fraction: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Shikamaru. Nothing to install.

What risk level is day_count_fraction? +

day_count_fraction is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit day_count_fraction? +

Yes. Add a rate_limit block to the day_count_fraction rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block day_count_fraction completely? +

Set action: deny in the PolicyLayer policy for day_count_fraction. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides day_count_fraction? +

day_count_fraction is provided by the Shikamaru MCP server (JayOfemi/shikamaru). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.