Skip to main content
Glama

OpsRev Roofing AI

List JobNimbus tasks

jobnimbus_list_tasks
Read-only

List tasks and appointments, optionally filtered to a specific contact or job jnid.

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

Input Schema

NameRequiredDescriptionDefault
fromNo
sizeNo
relatedIdNo
sortDirectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds almost nothing: with from/size parameters present it never mentions pagination, default page size, result ordering, or completeness of results — meaningful behavioral traits for a list tool that are left entirely undisclosed.

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?

A single, front-loaded sentence with no filler or repetition. It is efficient, though arguably too terse given the undocumented parameters.

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

Completeness2/5

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

With four parameters at 0% schema coverage and no output schema, the description should have explained paging and sorting behavior. It leaves an agent unable to determine how to page through results or what order they arrive in, which is essential for a list operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 full burden, but it only explains one of four parameters (relatedId, as contact or job jnid). The from/size pagination pair and sortDirection enum receive no explanation whatsoever, leaving the caller to guess offset semantics and defaults.

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?

The description names a specific verb and resource ("List tasks and appointments") and adds a qualifier about optional filtering. It is distinguishable from sibling readers like jobnimbus_list_activities and jobnimbus_list_jobs by naming tasks/appointments explicitly, though it doesn't call out the contrast with list_activities directly.

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?

The phrase "optionally filtered to a specific contact or job jnid" implies when the relatedId filter is useful, giving some usage context. However, there is no explicit when-to-use vs. when-not-to-use guidance, no mention of how it differs from list_activities or get_* tools, and no prerequisites for obtaining a jnid.

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