Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Save report HTML snapshot

trigger_report_refresh

Publishes or refreshes a project's report HTML through the admin-only report endpoint; set confirm=true, and a 403 means nothing was saved.

Instructions

POST project report HTML via projects/{id}/report/. That route is limited to deeptrue admins. Requires confirm=true. A 403 means the account is not an admin; nothing was saved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "html": "<html>"
    },
    "name": "trigger_report_refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesReport HTML payload accepted by projects/{id}/report/
confirmNo
project_idYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations cover only the side-effect profile (readOnlyHint=false, openWorldHint=false), so the description carries the auth and error burden and does so well. It states that the route is restricted to deeptrue admins, that confirm=true is required, and that a 403 means nothing was saved. The main gap is success behavior: it does not say whether the snapshot overwrites an existing report or what is returned.

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?

Four short sentences, front-loaded with the action and route, then the auth gate, the required flag, and the failure semantics. Nothing is filler, and the most important constraint, admin-only access, is surfaced early.

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?

This is a mutating, admin-gated tool with a nested HTML object and no output schema. The description covers preconditions and the most likely failure mode, which is the part an agent most needs. It falls short of full coverage because success-side behavior and project_id typing are left to the schema, which is only half documented.

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 50%. The description adds meaning for confirm, which the schema leaves undescribed, and for the html payload's destination route. It says nothing about project_id, including whether the string or number form is expected, or about the organization parameter's per-call, non-persisting behavior.

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?

The description names a specific action and resource: POSTing project report HTML to projects/{id}/report/. That is enough to distinguish it from read-side siblings like get_report and list_reports. The framing is slightly loose, since the tool name suggests a refresh while the title and description describe saving an HTML snapshot.

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 supplies the conditions that gate the call: an admin-only route and a mandatory confirm=true. It gives no explicit routing against alternatives, such as when to use this rather than update_project or a report-layout tool. The guidance is real but stops at preconditions.

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