Skip to main content
Glama
Sign In

BerthTime

by com.berthtime
OverviewDiscussionsAdmin

Support requests

list_support_requests
Read-onlyIdempotent

The company's support requests to the BerthTime team, most recent activity first. Use it to check the status of a request; to open one use create_support_request. Internal staff notes are never included. Optional: status (active = open + pending, the default; open, pending, resolved, closed or all), limit (1-100, default 20). Returns: tickets[] {id, number (BT-1234), subject, topic, status, priority, last_message_at, last_message_by, message_count, preview}, counts by status.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum requests returned, 1-100 (default 20).
statusNoactive = open + pending (default)active
companyNoWhich company to act for: its id, @handle or exact name (see list_companies). Omit for the connection's default company.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real value beyond them: internal staff notes are never returned (a data-visibility guarantee an agent cannot infer from annotations) and results are ordered by most recent activity. It does not discuss permissions or rate limits, but those are not clearly needed.

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 purpose, ordering and the create-path alternative, then the optional filters, then returns. Dense but every section is useful; the enumerated return fields are justified because there is no output schema, though the status enumeration slightly repeats the schema.

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 output schema, the description carries the return contract (ticket fields, status counts) and the exclusion of internal notes, which makes it callable without surprises. The only gap is that company scoping/default behavior is left entirely to 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 description coverage is 100%, so the parameter baselines at 3. The description restates the status enum semantics and limit range, which largely duplicates the schema rather than extending it, and it never mentions the `company` parameter that exists in the schema.

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 the resource precisely ('The company's support requests to the BerthTime team') along with the ordering ('most recent activity first'), so the agent knows exactly what it is retrieving and in what order. It also explicitly contrasts with the write path ('to open one use create_support_request'), separating it from adjacent tools.

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?

Gives a clear when-to-use ('check the status of a request') and names the alternative for the mutation case. It stops short of stating when this tool should not be used or naming the read siblings (e.g. list_shipments) as alternatives, so it is strong but not exhaustive.

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

All BerthTime 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