Skip to main content
Glama

Fidget Labs

Ask Fidget Labs

ask_fidget_labs
Read-onlyIdempotent

Ask a question about Fidget Labs in plain language and get the pages that answer it: services, engagements, industries, platforms, case studies, the pricing model, articles and glossary terms. Each result has a name, a URL and a description.

Use this first when you do not know which page covers something, for example "can they migrate us off Adobe Experience Manager" or "do they run paid media". Results are retrieval over the site's own index, not generated text.

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": {
      "query": "<query>"
    },
    "name": "ask_fidget_labs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many pages to return, 1 to 25. Defaults to 8.
queryYesThe question in plain language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely useful disclosures beyond that: the result shape (name, URL, description) and the framing that results are retrieval over the site's own index rather than generated text, which tells the agent not to expect synthesized answers. It does not discuss result limits, ranking, or what happens on an empty match, and the retrieval note is the description's main original contribution rather than a full behavioral picture.

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 short paragraphs: the first states what you get and its shape, the second says when to reach for it plus concrete examples. Front-loaded, no repetition of the title, and every sentence carries either scope or routing information.

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 two-parameter search tool with no output schema, the description supplies the missing return-shape information (name, URL, description) and sets expectations about result provenance. The only gap is operational: nothing about result limits beyond the schema default or behavior on no-match, which an agent might want before calling. That is a minor omission against an otherwise self-sufficient definition.

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?

The schema documents both parameters fully, including the limit range and its default, so the schema carries the burden. The description's example questions mildly illustrate what a well-formed 'query' looks like (natural-language, capability-oriented) but adds no syntax, format, or ranking semantics beyond the schema's "question in plain language." Baseline 3 applies at 100% coverage.

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 ("Ask a question about Fidget Labs ... get the pages that answer it") and enumerates the corpus it covers: services, engagements, industries, platforms, case studies, pricing model, articles, glossary. That scope enumeration, plus the note that results are pages with name/URL/description, lets an agent distinguish it from read_page 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 Guidelines4/5

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

Gives a clear selecting condition: "Use this first when you do not know which page covers something," which implicitly routes known-page lookups elsewhere. It also supplies two example questions that anchor the expected input style. It stops short of naming the alternative (read_page) or stating exclusions explicitly, so it is clear context without full when-not 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.