Skip to main content
Glama
Sign In

GigXchange

by app.gigxchange
OverviewDiscussionsAdmin

Search GigXchange help

search_help
Read-onlyIdempotent

Searches GigXchange's help articles — its own documentation of how the platform works (payments, fees, deposits, cancellations, bookings, profiles, messages, account, what to do when something goes wrong). Returns matching articles with their url, or no results when the help centre does not cover a topic.

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

Input Schema

NameRequiredDescriptionDefault
roleNoOptional: the member's role (artist, venue, agent, promoter, organiser) so role-specific articles rank first.
queryYesWhat the member wants to know, in their own words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 safety is covered. The description still adds real value by stating the return shape (matching articles with their url) and the failure mode (no results when uncovered), which the annotations cannot convey.

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 sentences, front-loaded with the verb and corpus, then the return/failure behavior. No filler and the parenthetical topic list earns its place by defining scope boundaries for the agent.

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?

There is no output schema, and the description compensates by describing the return (articles with url) and the empty-result case. With only two well-documented parameters and full annotation coverage, an agent has what it needs; naming the sibling help tools would make it complete.

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%, so both query and the optional role parameter (with its ranking effect) are documented in the schema. The description adds no additional syntax, format, or ranking detail beyond that, so the baseline 3 is appropriate.

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?

States a specific verb and resource (searches help articles) and scopes the corpus precisely with a topical enumeration (payments, fees, cancellations, etc.), so an agent understands the content domain. It does not explicitly differentiate itself from siblings like get_help_article or list_help_topics, which is why this lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied: use it for how-the-platform-works questions, and a 'no results' outcome signals the help centre doesn't cover the topic. However, no explicit when-to-use guidance relative to get_help_article or list_help_topics is given, leaving the agent to infer which help tool to pick.

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

All GigXchange toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources