Skip to main content
Glama

OpsRev Roofing AI

Add a CompanyCam project comment

companycam_add_project_comment

Post a comment to a known project under the connected CompanyCam account. Confirm the project and exact comment with the user before posting.

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>",
      "content": "<content>"
    },
    "name": "companycam_add_project_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds real value beyond them by requiring explicit user confirmation before the write and by scoping the action to the connected account. It omits that non-idempotent retries could create duplicate comments, and says nothing about whether a posted comment can be edited or removed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed immediately by the safety pre-condition. Every clause carries information an agent needs; nothing is redundant or buried.

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 simple two-parameter write tool whose annotations already cover the safety profile, the definition covers the essential action and the confirmation workflow. With no output schema, though, a sentence on what comes back (e.g., the created comment or its ID) would close the remaining gap.

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 must carry parameter meaning: it clarifies that projectId refers to an existing/verified project and that content is the exact comment text to be confirmed with the user. It does not mention the schema's numeric-string pattern for projectId or the 2000-character cap on content, so it only partially compensates for the undocumented 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?

Uses a specific verb and resource ("Post a comment to a known project") plus a scope qualifier that this targets an already-identified project, which implicitly separates it from discovery tools like companycam_find_projects. It does not name 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?

"Known project" implies a prerequisite (the projectId must come from a prior lookup) and the description adds a concrete procedural rule: confirm the project and exact comment with the user before posting. However, it never says when to use this versus alternatives or which tool to call first, so usage is only implied.

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