DevTune MCP

devtune_get_intelligence_forecast

Read-onlyIdempotent

Forecast short-term primary citations and presence-rate direction using recent project visibility trends. Presence-rate values are ratios from 0 to 1 and are null when no response has usable citation data. With no data in the window, confidence values and trend are null.

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

Input Schema

Name	Required	Description	Default
`windowDays`	No	Rolling window in days: 30 or 90. Defaults to 30.
`horizonDays`	No	Forecast horizon in days: 7, 14, 30, 60, or 90.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 9, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety. Beyond that the description adds genuinely useful disclosure: presence-rate values are 0–1 ratios and null when no response has usable citation data, and confidence/trend are null when the window is empty. This is meaningful edge-case behavior an agent could not get from annotations.

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?

Three sentences, front-loaded with the purpose, followed by the two null-behavior rules. No filler; each sentence carries information.

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 no output schema, the description does carry some return-value burden, and it handles the important null semantics for presence-rate, confidence, and trend. It does not describe the full shape of the forecast payload, but it is adequate for a 2-param read tool.

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 coverage is 100%, and both windowDays and horizonDays have enum values and defaults documented in the schema. The description adds nothing about the parameters, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Forecast short-term primary citations and presence-rate direction using recent project visibility trends.' An agent understands exactly what is produced. It does not differentiate from siblings like get_visibility_summary or get_citation_stats, which report history rather than forecast.

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

Usage Guidelines2/5

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

No guidance on when to choose a forecast over the many sibling visibility/citation tools, and no exclusions or prerequisites. The phrase 'using recent project visibility trends' is context about the input, not selection guidance.

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

All DevTune MCP tools Inspect

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

Need Help?