Skip to main content
Glama

Attendance by subject

get_subject_frequency
Read-only

Get attendance counts and ratios per subject, optionally within a window of up to 371 days. For overall totals use get_attendance_frequency.

Instructions

Get attendance counts and ratios per subject, optionally within a window of up to 371 days. For overall totals use get_attendance_frequency.

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": {
      "account_alias": "<account_alias>"
    },
    "name": "get_subject_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoLast day, YYYY-MM-DD, inclusive; at most 370 days after the first.
date_fromNoFirst day, YYYY-MM-DD, inclusive.
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
itemsYes
date_toYes
identityYes
date_fromYes
paginationNo
observationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.1
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
  2. Changed2 schema fields changedv2.5.0
    • removedOutput schema / $defs / Pagination / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -false
  3. Changed4 schema fields changedv2.3.1
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
    • addedInput schema / properties / date_from / description
      Added value: +"First day, YYYY-MM-DD, inclusive."
    • addedInput schema / properties / date_to / description
      Added value: +"Last day, YYYY-MM-DD, inclusive; at most 370 days after the first."
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context in the form of the per-subject grouping and the ~371-day window cap, but says nothing about result shape, ordering, or handling of empty subjects beyond what the output schema presumably covers.

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 tight sentences: the capability and window constraint come first, the disambiguation second. Every clause carries information and there is no filler.

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?

With an output schema, full schema description coverage, and explicit annotations, the description only needs to convey purpose, scope, and routing—all of which it does. Minor gaps remain: it does not say what happens when dates are omitted (implicitly all-time) or that account_alias is required.

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%, including format and default details for date_from/date_to and the account_alias source ('list_accounts'), so the schema carries the parameter semantics. The description's mention of 'a window of up to 371 days' reinforces the date-range intent but adds no format or edge-case detail beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ('Get attendance counts and ratios per subject') plus the optional scoping window, and explicitly contrasts itself with get_attendance_frequency for overall totals. An agent can distinguish this from the sibling aggregate tool without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool (get_attendance_frequency) and the condition that selects it ('For overall totals'). This is explicit when-to-use-which routing rather than implied guidance, leaving no ambiguity about which of the two aggregate tools to call.

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