Skip to main content
Glama

Group and measure projects

analyze_projects
Read-onlyIdempotent

Counts and mix for matching projects, grouped by up to three fields (city, county, state, building type, meetingMonth, and the others describe_data lists). Returns group keys and aggregates, not project names or contacts. Each metric includes a coverage fraction. Groups under five projects are omitted. Does not use credits.

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

Input Schema

NameRequiredDescriptionDefault
limitNoGroups to return. Free — this is not a record count.
datasetNoDefaults to "projects".
filtersNoThe same filters get_projects takes, as an object.
groupByNoUp to 3 field names from describe_data, e.g. ["city","constructionType"].
metricsNoMetric names from describe_data. Defaults to ["count"].
orderByNo
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds real behavioral context: results contain group keys and aggregates rather than project names or contacts, each metric carries a coverage fraction, groups under five are suppressed, and the call consumes no credits. Small-group suppression and credit cost are exactly the kind of facts an agent cannot derive from annotations or schema.

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?

Six short sentences, front-loaded with what is counted and how it is grouped, then the return shape, then behavioral caveats. Nearly every clause earns its place, though the opening 'Counts and mix' is slightly clipped and the field enumeration in parentheses is denser than needed.

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 seven parameters, a free-form nested filters object, and no output schema, the description does the important work: it defines the return shape conceptually, explains the coverage fraction and suppression rule, and points to describe_data for valid field and metric names. Remaining gaps are ordering semantics and the filter object's internal shape, both partially covered by the schema.

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 71%, so the schema already documents limit, dataset, filters, groupBy and metrics. The description reinforces groupBy's three-field cap and gives concrete example field names, but it adds little on orderBy, direction, or the shape of the nested filters object beyond deferring to get_projects. 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?

States a specific verb and resource — counts and mix for projects, grouped by up to three fields — which clearly signals an aggregation tool rather than a record-listing one like get_projects. The parenthetical field examples and the 'returns group keys and aggregates, not project names' line sharpen the distinction. It stops short of naming a sibling it replaces, which is the only thing separating it from a 5.

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?

Usage is implied rather than stated: an agent can infer this is the tool for grouped aggregation instead of raw retrieval, and the reference to get_projects' filters and describe_data's field lists points at dependencies. However, there is no explicit 'use this when X, use count_projects instead when Y' routing, and no prerequisites are spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources