Skip to main content
Glama

Operations Scorecards Tool

operations-scorecards
Read-only

Reads bounded technician performance and coaching signals for the authenticated workspace without exposing coaching notes or private contact fields. Use to compare technician scorecards in the connected business. Returns scorecards, total, summary, filters, scope.

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": "operations-scorecards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum jobs sampled per technician.
technician_idNoOptional same-business technician ID.

Output Schema

NameRequiredDescriptionDefault
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
totalYesTotal for the returned result.
filtersYesFilters metadata; empty collections retain their existing JSON array representation.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.
scorecardsYesBounded scorecards records returned by this tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "filters": {
      +      "description": "Filters metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "scorecards": {
      +      "description": "Bounded scorecards records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "description": "Total for the returned result.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "scorecards",
      +    "total",
      +    "summary",
      +    "filters",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are bounded, scoped to the authenticated workspace, and deliberately exclude coaching notes and private contact fields, which is exactly the kind of disclosure an agent cannot get from structured fields.

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?

Three short sentences with the privacy and scoping constraints front-loaded, so the agent reads the important qualifiers first. The trailing 'Returns scorecards, total, summary, filters, scope' is largely redundant given an output schema exists, which is the only real waste.

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

Completeness5/5

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

For a two-optional-parameter read tool with full schema coverage, full annotation coverage, and an output schema, the description supplies everything still missing: the privacy boundary, workspace scoping, and bounded sampling. Nothing an agent needs in order to call it correctly is absent.

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 100%, so both parameters (limit, technician_id) are already documented, including the 1-50 bound. The description only echoes bounding via 'bounded' and adds no syntax, format, or interaction detail beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ('Reads') with a specific resource ('bounded technician performance and coaching signals'), and the second sentence narrows it to 'technician scorecards.' It is clear what the tool returns, though it never contrasts itself with any sibling analytics tool such as reports-overview or reports-by-location.

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?

'Use to compare technician scorecards in the connected business' gives a clear intended use, but there is no when-not guidance, no mention of alternatives for workspace-wide reporting, and no prerequisites spelled out for the authenticated workspace context.

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