Skip to main content
Glama

Report filter options

portal_reports_options
Read-onlyIdempotent

The valid filter values for portal_reports_get on your account: date presets, granularities, service groups (and whether each is available to you) and your own project codes with titles (wrapped as data). Use it to build a valid project filter.

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

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of project titles. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read. The description adds account scoping ('on your account'), notes that service-group entries carry per-user availability, and flags that project codes come with titles 'wrapped as data' — relevant context an agent would not get from the annotations alone, especially for a tool whose output feeds another call.

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?

One sentence of content plus one sentence of usage guidance, with the returned categories front-loaded. Slightly dense due to nested parentheticals, and 'wrapped as data' reads opaquely on first pass, but no sentence is wasted.

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?

For a one-optional-param read tool with strong annotations and no output schema, the description does the main remaining job: enumerating what the response contains and what it is for. The shape of the returned values (e.g., how presets and granularities are keyed) is left unspecified, which is a minor gap for a tool meant to feed another call.

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?

There is a single optional parameter (locale) whose enum and default are fully documented in the schema at 100% coverage. The description adds nothing about locale or how it affects the returned project titles, so it sits at the baseline set by the schema.

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 names the resource precisely (valid filter values: date presets, granularities, service groups, project codes) and ties it to the sibling portal_reports_get, so an agent can tell it is the options/lookup companion rather than the report fetcher. It lacks an explicit verb ('returns'/'lists'), but the enumeration of contents leaves no ambiguity about what comes back.

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?

Usage is stated directly: 'Use it to build a valid project filter', which tells the agent to call this before portal_reports_get when constructing filter arguments. There is no explicit when-not or mention of caching/staleness, but the trigger condition is clear enough for correct selection.

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