Skip to main content
Glama
Sign In

EverythingMeetsAI

by com.everythingmeetsai
OverviewDiscussionsAdmin

List outlets

list_outlets
Read-onlyIdempotent

Outlets that cover at least one published story, with slug, name, homepage and story count; optionally within one sector. Use the slug in search_stories' outlet filter.

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

Input Schema

NameRequiredDescriptionDefault
sectorNoOne sector slug. Sector slugs: see list_sectors (e.g. healthcare_life_sciences, law, retail, regulation_government, financial_services, manufacturing_robotics).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld=false). The description adds a genuinely useful behavioral constraint that the annotations do not: only outlets with at least one published story are returned, so coverage is filtered rather than exhaustive. It omits pagination/ordering behavior, keeping it out of the top band.

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?

Two tight clauses: the resource/scope statement comes first, followed by the actionable handoff sentence. Nothing is padding, though the semicolon-joined field list makes the first sentence slightly dense.

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?

With no output schema, the description compensates by enumerating the returned fields and the filtering rule, and it explains how the result is consumed downstream. For a one-optional-parameter list tool this is nearly complete; only result-size/pagination behavior is unaddressed.

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 sector parameter already documents that it takes one sector slug and points to list_sectors for valid values. The description's 'optionally within one sector' only restates optionality the schema already conveys, adding no new semantics.

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 names a precise resource and scope: outlets that cover at least one published story, with the fields returned (slug, name, homepage, story count). The 'list' verb is implicit rather than stated, and it doesn't explicitly contrast with list_sectors/list_types, but the search_stories handoff makes its role distinguishable.

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 a concrete downstream usage rule — take the slug and feed it into search_stories' outlet filter — and notes the sector filter is optional. There is no explicit when-not-to-use or prerequisite guidance (e.g., auth, whether it paginates), so it stops short of a full routing rubric.

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

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