Skip to main content
Glama

OpsRev Roofing AI

Find CompanyCam projects

companycam_find_projects
Read-only

Find projects by name or street address, or list projects if query is omitted. Use meta.next_cursor as after for the next page.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real operational context the annotations do not: that results are cursor-paginated and that meta.next_cursor should be fed back as the after parameter. It does not mention result limits or total counts, which keeps it from a 5.

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, zero filler. The primary behavior is front-loaded and the pagination hint follows as a secondary clause.

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 two-parameter read-only search with no output schema, the description covers invocation, the no-query case, and pagination. The only real gap is that the response shape is only hinted at through meta.next_cursor and nothing describes what a returned project record contains.

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 0%, so the description must carry both parameters, and it largely does: query is scoped to name or street address with an explicit omitted-means-list semantics, and after is defined via meta.next_cursor. It omits match behavior (substring vs exact) and case sensitivity, but both parameters are otherwise usable from the text alone.

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 verb and resource ('Find projects') plus the searchable fields (name or street address) and the no-query fallback to listing all projects. That dual behavior is clearer than most search tools, though it never names companycam_get_project to distinguish lookup-by-id from lookup-by-name.

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?

Gives one concrete usage condition ('list projects if query is omitted') and a pagination instruction, but offers no when-not guidance or routing to the sibling that fetches a single project. Usage is implied rather than fully specified.

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