Skip to main content
Glama
Sign In

AlphaWeb

by ai.alphaweb.mcp
OverviewDiscussionsAdmin

competitors_list

Read-only

Competitor intel: tracked competitors/coverage/monitoring/digest/signals.

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": {
      "workspace": "<workspace>"
    },
    "name": "competitors_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNo
limitNo
cursorNo
statusNo
workspaceYes
include_digestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds nothing beyond that—no note on ordering, pagination via cursor, or what 'digest' inclusion means behaviorally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than economy—a slash-delimited keyword list is not front-loaded prose and gives no actionable structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter list tool with no output schema, the description should at minimum describe what is listed and how pagination/filtering work. Neither is present, leaving the agent to infer results and cursor behavior from the schema alone.

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

Parameters2/5

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

Six parameters with 0% schema description coverage, so the description carries the full burden and fails: role, status, limit, cursor, include_digest and workspace are never explained. The words 'monitoring' and 'digest' only loosely gesture at status and include_digest; cursor and limit semantics remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a keyword fragment ('tracked competitors/coverage/monitoring/digest/signals') with no verb and no statement of what is actually returned or done. It hints at the domain (tracked competitors) but does not distinguish the tool from siblings like competitor_scans_list or competitor_ads_list.

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 when-to-use statement, no mention of alternatives, and no prerequisites. The slashes suggest features exist but give no signal about which situation calls for this list versus competitors_save or competitor_scans_list.

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

All AlphaWeb 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