Skip to main content
Glama

Jobs Today Tool

jobs-today
Read-only

Lists authorized jobs scheduled for a business day, with bounded customer, schedule, status, and technician fields. Use to list today’s jobs in the connected business. Returns date, timezone, jobs, summary, 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": "jobs-today"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoLocal business date, YYYY-MM-DD; defaults to today.
limitNoMaximum number of jobs to return.
statusNoOptional job status filter.
technician_idNoOptional technician ID.

Output Schema

NameRequiredDescriptionDefault
dateYesDate used or returned by this tool.
jobsYesBounded jobs records returned by this tool.
scopeYesAuthorization scope of this result; data remains restricted to the connected business.
summaryYesSummary metadata; empty collections retain their existing JSON array representation.
timezoneYesTimezone used or 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": {
      +    "date": {
      +      "description": "Date used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "jobs": {
      +      "description": "Bounded jobs records returned by this tool.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "scope": {
      +      "description": "Authorization scope of this result; data remains restricted to the connected business.",
      +      "enum": [
      +        "connection_business"
      +      ],
      +      "type": "string"
      +    },
      +    "summary": {
      +      "description": "Summary metadata; empty collections retain their existing JSON array representation.",
      +      "type": [
      +        "object",
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "timezone": {
      +      "description": "Timezone used or returned by this tool.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "timezone",
      +    "jobs",
      +    "summary",
      +    "scope"
      +  ],
      +  "type": "object"
      +}
  2. 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 readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral details beyond that: results are limited to "authorized" jobs (permission scoping) and carry "bounded" fields (a trimmed projection). It says nothing about pagination or truncation despite a limit capped at 50.

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, front-loaded with the action and scope, with no filler. The final sentence enumerating return keys ("date, timezone, jobs, summary, scope") is partly redundant since an output schema exists, which keeps it just below top marks.

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 read-only, four-parameter listing tool with full schema coverage, an output schema, and complete annotations, the description covers purpose, scope, and the return envelope. The only real gap is guidance on how this differs from the search-jobs sibling, which is an agent-facing routing concern rather than a missing behavior.

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 date, limit, status, and technician_id are already documented with formats, defaults, and bounds. The description contributes no additional input semantics; "customer, schedule, status, and technician fields" describes returned fields rather than parameters.

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 opens with a specific verb and resource ("Lists authorized jobs scheduled for a business day") and scopes the result set with named field families. It never names the obvious sibling search-jobs, so the boundary between a single-day listing and a general search is left implicit.

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 list today's jobs in the connected business" gives a clear positive use case, but there are no exclusions and no mention of when to prefer search-jobs instead. The date parameter allows any day, so the description's "today" framing does not resolve the overlap with the search sibling.

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