Skip to main content
Glama

OpsRev Roofing AI

List CompanyCam project comments

companycam_list_comments
Read-only

Read field comments for a known CompanyCam project. Use meta.next_cursor as after for the next page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "companycam_list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered for free. The description adds one genuinely behavioral fact – that the response is cursor-paginated via meta.next_cursor – but says nothing about ordering, result caps, or permission requirements for reading field comments.

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?

Two sentences, no filler, and the core operation is front-loaded before the pagination hint. It is lean to the point of being skeletal – nothing wasted, but also nothing elaborated.

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

Completeness3/5

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

For a two-parameter read tool with no output schema, the definition covers the call mechanics (required project, pagination cursor) but leaves the return shape only inferable through the meta.next_cursor mention. It is adequate to invoke correctly, not quite enough to predict what comes back.

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 0%, so the description carries the burden for both parameters. It handles `after` well by tying it to meta.next_cursor from a prior response, which is real meaning the bare schema does not convey, but it adds nothing about projectId beyond calling it 'known' (no format, no source of the ID).

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?

'Read field comments for a known CompanyCam project' pairs a specific verb (read) with a specific resource (field comments) and scopes it to a project, which implicitly separates it from companycam_add_project_comment. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

'for a known CompanyCam project' implies the prerequisite that the caller must already have a projectId, and the second sentence tells the caller exactly what to do when they want more pages. There is no explicit when-not guidance and no mention of alternatives such as fetching the project itself, so usage is implied rather than 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