Skip to main content
Glama

FarmTempo

onboard_roles

Read-onlyIdempotent

[B2AI] 팜템포 참여 역할 목록과 각 역할의 개설 상태.

CLOSED 역할은 응답에 포함되지 않는다(가입 경로가 없다). WAITLIST 는 대기 등록만 가능하며 아직 거래가 열리지 않은 상태다.

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_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavior beyond that: CLOSED roles are silently omitted from the response because there is no signup path, and WAITLIST means waitlist-only registration with trading not yet open — useful filtering and semantics an agent would otherwise not know.

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 resource description followed by the two status semantics that matter. Every sentence carries information; only the bracketed "[B2AI]" tag and the missing verb are minor inefficiencies.

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?

For a zero-parameter, non-destructive read with no output schema, the description covers the key gotcha (CLOSED roles are absent) and the WAITLIST meaning. However, it never states the other status values (e.g. OPEN), the ordering of results, or whether the list reflects the caller's own eligibility, leaving the return-shape story partially incomplete despite the tool's simplicity.

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?

The input schema has zero parameters and 100% coverage, so there is nothing for the description to disambiguate. Baseline 4 applies since no parameter semantics are needed.

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 is a noun phrase ("participating role list and each role's open status") that makes clear what is returned, but it has no explicit verb for the operation and gives no hint about how this differs from siblings such as onboard_stats. An agent can guess it is a listing tool, but the purpose is implied rather than stated.

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 call this versus other onboarding or status tools, and no prerequisites are mentioned. The sentences about CLOSED and WAITLIST describe how to interpret results, not when to select this tool, so the usage guidance is absent.

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