Skip to main content
Glama

My service requests

requests_list
Read-onlyIdempotent

Your own service, software, quote and other requests with Barmaan, newest first: reference, kind, category, title, real status, dates, files count. Filter by status (received, in_review, quoted, in_progress, completed, closed, open, done, all), kind, category (calibration, engineering, maintenance, software, other) or q (text or reference). Also returns counts. Page with next_cursor.

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

Input Schema

NameRequiredDescriptionDefault
qNoText or reference.
kindNo
limitNo
cursorNoValue of next_cursor from the previous page.
statusNo
categoryNo

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 establish read-only, idempotent, closed-world, non-destructive behavior, and the description adds genuinely new context on top: results are scoped to the caller's own requests only, sorted newest first, and count aggregates are returned alongside the page. Pagination behavior is disclosed via 'Page with next_cursor', which is the kind of trait annotations cannot carry.

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 what is returned before the filtering parentheticals, and every clause carries information. It is dense to the point of being a run-on, but there is no filler sentence to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly enumerates the returned fields and notes the accompanying counts; pagination is explained via next_cursor. For a six-parameter, zero-required list tool with strong annotations, everything an agent needs to call it correctly is present.

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?

Schema description coverage is only 33%, so the description must compensate, and it largely does: it spells out the full allowed status set, the category values, that q matches text or reference, and that cursor is the previous page's next_cursor. The gap is 'kind', whose nine enum values are never named in the description, and 'limit' is not mentioned at all.

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 resource and scope — 'Your own service, software, quote and other requests with Barmaan' — and enumerates the returned fields (reference, kind, category, title, real status, dates, files count). It does not differentiate itself from the sibling 'my_requests', so the read-only personal-list intent is clear but the boundary with a very similarly named sibling is not.

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: the filtering and paging mechanics tell an agent how to call it, but there is no explicit 'use this when / use X instead' guidance. Nothing routes the agent between this tool, 'my_requests', and 'get_service' for single-record retrieval.

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