Skip to main content
Glama

Fidget Labs

List Fidget Labs offers

list_offers
Read-onlyIdempotent

List every engagement Fidget Labs offers: the situation it answers, what it includes, the outcome, how it is contracted and who leads it. The same list as https://fidgetlabs.io/how-we-engage. There are no prices or durations: every engagement is scoped to the client (engagement: "scoped"). For cost, point people to /contact.

Use this when someone asks what Fidget Labs offers, or which engagement fits a stalled program, an AI cost question, or a platform choice.

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

Input Schema

NameRequiredDescriptionDefault
limitNoOffers to return, 1 to 50. Omit it for all of them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 closed-world scope, so the safety profile is covered. The description adds genuinely non-obvious behavior: there are no prices or durations, every engagement is "scoped," and the output mirrors a public page. It stops short of saying how many items typically come back or how results are ordered.

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?

The purpose and the item shape come first, then the usage trigger, then the cost caveat — a sensible front-loading order. The prose is slightly verbose with a mid-sentence line break, but no sentence is filler; each conveys a distinct fact.

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?

There is no output schema, so the description must convey what comes back, and it does by enumerating the per-offer fields. Combined with the no-prices caveat and the /contact redirect, an agent has everything needed to call this and to answer the follow-up cost question correctly.

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 coverage is 100% and the single `limit` parameter is already documented as "1 to 50, omit for all." The description says nothing about limiting or pagination, so it adds no meaning beyond the schema. Baseline 3 applies when the schema carries the full parameter burden.

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 ("List every engagement Fidget Labs offers") and then enumerates the shape of each item: situation, contents, outcome, contracting model, lead. It is clearly distinguishable from ask_fidget_labs and read_page in spirit, but it never names or contrasts those siblings explicitly.

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

Usage Guidelines4/5

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

It gives concrete triggering contexts ("what Fidget Labs offers," a stalled program, an AI cost question, a platform choice) and adds a useful redirect: for cost, point people to /contact. What is missing is an explicit statement of when to prefer a sibling, e.g. when a free-form question needs ask_fidget_labs rather than the fixed offer list.

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.