Skip to main content
Glama

FarmTempo

onboard_stats

Read-onlyIdempotent

[B2AI] 참여 현황 공개 집계 — 역할별·시군구별 실제 건수만.

⛔ 개인 식별 정보(상호·연락처·정확 좌표)는 어떤 필드로도 나가지 않는다. 숫자가 0인 구간도 0으로 그대로 돌려준다(보정·반올림 없음).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive, so the description does not need to cover safety. It does add real behavior the annotations lack: no PII (business names, contacts, exact coordinates) is ever returned, and empty buckets are returned as literal zeros with no rounding or adjustment. Those are genuine output guarantees an agent can rely on.

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?

Three short lines, front-loaded with what is counted and at what granularity, followed by the privacy constraint and the zero-handling rule. No wasted sentences; the ⛔ marker is stylistic but flags the constraint clearly.

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 zero-parameter read-only aggregate with no output schema, the description should carry the shape of the result, and it largely does: per-role and per-district counts, zeros preserved, no personally identifying fields. It could go slightly further by noting whether the output is a flat table or nested by dimension, which matters because no output schema exists.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so the baseline is 4. The absence of arguments matches the description of a whole-population aggregate, and nothing implies hidden filtering options that an agent would look for in the schema.

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 states a concrete resource and scope: a public aggregate of participation counts broken down by role and by city/county/district, counting actual occurrences only. That is specific enough to separate it from the role-listing sibling onboard_roles, though the 'B2AI' prefix and implied verb leave the domain slightly opaque.

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?

The description says nothing about when to use this tool versus the related tools (for example onboard_roles or region_list): no prerequisites, no conditions, no named alternatives. The grouping context ('participation aggregates') implies how to use it, but that is inference rather than guidance.

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