Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

report_custom_dimension_delete

Destructive

Delete one tenant custom report property from a virtual Business Context entity type.

The tool preserves all other custom dimensions on the target entity type.

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": {
      "key": "<key>"
    },
    "name": "report_custom_dimension_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesDimension key to delete, e.g. is_intercompany
viewNoAnalytics view to update, e.g. customers, vendors, chart_of_accounts
entity_typeNoEntity type to update, e.g. customer, vendor, gl_account
entity_type_idNoExact entity type definition ID to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds useful blast-radius context by saying only one property is removed and all other custom dimensions are preserved. It does not cover irreversibility, required permissions, or behavior when the key does not exist.

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?

It consists of two short sentences with no waste. The core action is front-loaded, and the preservation guarantee follows immediately as a scoping constraint.

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?

For a destructive four-parameter tool with no output schema, the description covers the action and the blast radius but not the failure modes or return behavior. It is adequate to select the tool but leaves gaps for correct invocation.

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 description coverage is 100%, so all four parameters (key, view, entity_type, entity_type_id) are documented in the schema with examples. The description adds no meaning about parameters, such as how entity_type and entity_type_id interact, or whether view is optional when entity_type_id is supplied. Baseline 3 is appropriate.

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 gives a specific verb and resource: 'Delete one tenant custom report property from a virtual Business Context entity type.' That is unambiguous and implicitly distinguishes it from the sibling tools report_custom_dimension_upsert and report_custom_dimensions_list, though those siblings are never named.

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?

The description does not state when to use this tool instead of report_custom_dimension_upsert, what prerequisites exist, or when deletion is appropriate. It also does not warn against deleting a dimension that existing reports or queries depend on. The only guidance is implied by the word 'Delete'.

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

All Spaces by Peakflo toolsInspect
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