Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

report_schema

Read-only

List available analytics views with their descriptions.

Report views cover data synced from connected systems (for example accounting: bills, invoices, payments). Data the workspace keeps itself lives in data tables (table_list); check those too when a view has no rows.

Returns a compact summary of each view — name, description, and counts of available measures, dimensions, and segments.

Use this first to discover what data is available, then call report_schema_detail with a specific view name to see its full measures, dimensions, and segments before building a report_query.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description still adds real behavior: what the return payload contains (name, description, counts of measures, dimensions, segments), the data scope (synced from connected systems such as accounting bills, invoices, payments), and the empty-view troubleshooting path. It does not discuss result limits or ordering, which is a minor residual gap.

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?

Front-loaded with the one-line purpose, then scope, then return shape, then usage sequence — a sensible ordering with no filler sentences. Slightly long for a zero-argument list tool; the parenthetical accounting example is helpful but the middle paragraph could be tightened.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so explicitly (compact summary of name, description, and measure/dimension/segment counts). What is missing is minor: no indication of how many views are returned or whether very large workspaces are truncated.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and no parameter explanation is needed. The description correctly spends its words on scope and next-step routing instead of inventing parameter guidance.

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?

States a specific verb and resource ('List available analytics views with their descriptions') and immediately scopes it against siblings by noting that workspace-owned data lives in data tables (table_list) rather than views. An agent can tell this apart from report_schema_detail and table_list 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.

Usage Guidelines5/5

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

Gives explicit sequencing: 'Use this first to discover what data is available, then call report_schema_detail with a specific view name ... before building a report_query.' It also names a conditional alternative ('check those too when a view has no rows' -> table_list), which is a when-not-to-use signal.

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