Skip to main content
Glama
Sign In
diagram-forge

diagram-forge

by jessepike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_usage_report

Retrieve usage and cost reports for diagram generations over a chosen period, with results grouped by provider, diagram type, or day.

Instructions

Get usage and cost report for diagram generations.

Args: days: Number of days to report on (default: 30) group_by: Group results by 'provider', 'diagram_type', or 'day'

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

Input Schema

NameRequiredDescriptionDefault
daysNo
group_byNoprovider

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It accurately states the core behavior (getting a report) but does not explicitly note that it is read-only or describe the output format. The 'get' wording implies safety, and the description is not misleading, but it lacks depth.

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 concise and well-structured. The first sentence states the purpose, and the Args list provides parameter details without unnecessary fluff. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, so the description should ideally describe the report's structure or contents. It does not mention what fields or format the report includes. The parameters are well-covered, but the output is left undefined, which is a gap for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no descriptions, so the Args section in the description is essential. It fully explains both parameters: 'days' as the report period and 'group_by' with allowed values. This goes beyond the schema's minimal structure.

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's function with a specific verb ('Get') and resource ('usage and cost report for diagram generations'). It is distinct from sibling tools which focus on diagram generation and configuration.

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

Usage Guidelines4/5

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

The description provides clear context that this tool is for reporting, and no sibling tool overlaps with this purpose. It does not explicitly mention alternatives or exclusions, but the role is obvious from the tool's unique function.

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

Deploy Server

Other Tools