Field Service Business Platform by Doing Work

shops_sendPermissions

What each role may send to a customer: quotes, invoices and visit recaps. The owner always may, for every job, and is not listed. Office starts able to send all three for any job. A lead starts able to send all three for jobs on their crew. A field worker starts able to send all three for jobs assigned to them. The owner can turn any of these off. A missing row means the default, which is on.

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": {
      "shop_id": "<shop_id>"
    },
    "name": "shops_sendPermissions"
  }
}

Input Schema

Name	Required	Description	Default
`shop_id`	Yes

Output Schema

Name	Required	Description	Default
`owner`	Yes
`roles`	Yes
`shop_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It describes permission defaults and owner overrides, but it does not say whether the tool reads or mutates permissions, what permissions are required, or what side effects occur.

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?

The description is tightly written, with no wasted sentences, and the role-default rules are presented in a logical order. However, it front-loads the domain model rather than stating the tool's operation, which weakens its usefulness despite the efficient prose.

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?

The output schema covers return values, and the description thoroughly explains the default permission model, including owner override and missing-row behavior. But it omits the operational purpose and shop_id scoping, leaving an agent unsure whether the tool reads or writes permissions.

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?

The single required parameter, shop_id, is never mentioned in the description, and schema description coverage is 0%. The description does not compensate by explaining what shop_id identifies or how it scopes the result.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains what send permissions govern (quotes, invoices, visit recaps) and how defaults work by role, but it never states the tool's operation. It is not clear whether this tool retrieves permission settings, updates them, or performs some other action, and it does not distinguish itself from siblings such as members_permissions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions. The role-default explanation is domain context, not invocation guidance.

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

All Field Service Business Platform by Doing Work tools Inspect

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

Need Help?