report_templatesList the built-in report layouts (freelancer weekly, agency client update, standup digest) and the sections each one covers. Use when the user asks what report styles exist or which sections to include. Do NOT use to build a report; use create_weekly_report or render_report_text.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| templates | Yes | Built-in report templates. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "templates": {
+ "description": "Built-in report templates.",
+ "items": {
+ "properties": {
+ "id": {
+ "description": "Template id, e.g. freelancer-weekly.",
+ "type": "string"
+ },
+ "name": {
+ "description": "Human-readable template name.",
+ "type": "string"
+ },
+ "sections": {
+ "description": "Sections the template covers, in order.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "sections"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "templates"
+ ],
+ "type": "object"
+}Output schema / (root)Previous value: -{
- "properties": {
- "results": {
- "description": "List of report templates entries.",
- "items": {
- "properties": {
- "created_at": {
- "description": "Timestamp when the template was created",
- "format": "date-time",
- "type": "string"
- },
- "description": {
- "description": "Brief description of the report template",
- "type": "string"
- },
- "template_id": {
- "description": "Unique identifier for the report template",
- "type": "string"
- },
- "template_name": {
- "description": "Name of the report template",
- "type": "string"
- },
- "template_type": {
- "description": "Type of the report template (e.g., freelancer, agency, standup)",
- "type": "string"
- },
- "updated_at": {
- "description": "Timestamp when the template was last updated",
- "format": "date-time",
- "type": "string"
- }
- },
- "required": [
- "template_id",
- "template_name",
- "template_type"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "required": [
- "results"
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "results": {
+ "description": "List of report templates entries.",
+ "items": {
+ "properties": {
+ "created_at": {
+ "description": "Timestamp when the template was created",
+ "format": "date-time",
+ "type": "string"
+ },
+ "description": {
+ "description": "Brief description of the report template",
+ "type": "string"
+ },
+ "template_id": {
+ "description": "Unique identifier for the report template",
+ "type": "string"
+ },
+ "template_name": {
+ "description": "Name of the report template",
+ "type": "string"
+ },
+ "template_type": {
+ "description": "Type of the report template (e.g., freelancer, agency, standup)",
+ "type": "string"
+ },
+ "updated_at": {
+ "description": "Timestamp when the template was last updated",
+ "format": "date-time",
+ "type": "string"
+ }
+ },
+ "required": [
+ "template_id",
+ "template_name",
+ "template_type"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "results"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the layouts are built-in and that section coverage is returned, which is useful but modest; it discloses no additional operational traits such as caching or refresh behavior. With annotations carrying the safety burden, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences: what it returns, when to use it, when not to and what to use instead. Front-loaded with the resource and zero wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter read-only listing tool with an output schema already documenting the return shape, the description supplies everything needed: the content returned, the trigger, and the routing to the correct sibling for report generation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no inputs are required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb (List) plus resource (built-in report layouts) with concrete examples of the layouts and a statement of what each entry covers (sections). It is clearly distinguishable from the sibling build/render tools without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit positive trigger (user asks what report styles exist or which sections to include) and an explicit negative trigger with named alternatives (do NOT use to build a report; use create_weekly_report or render_report_text). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.