Skip to main content
Glama
ethank64

yellow-pages

by ethank64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
YELLOW_PAGES_TRANSPORTNoTransport mode ('stdio' or 'streamable-http'). Default: stdiostdio
YELLOW_PAGES_CHROMA_DIRNoChroma vector DB directory. Default: ./chroma_db_agent_tools_v9./chroma_db_agent_tools_v9
YELLOW_PAGES_SCHEMA_PATHNoOpenAPI schema file (JSON or YAML). Default: ./sample_schema.json./sample_schema.json
YELLOW_PAGES_EMBEDDING_MODELNoHuggingFace/sentence-transformers model name. Default: sentence-transformers/all-MiniLM-L6-v2sentence-transformers/all-MiniLM-L6-v2

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
discover_operationsA
Discover which API operations match a natural-language query. Uses RAG over the
loaded OpenAPI schema; returns a list of operation entries (operation name, method,
url, parameters with name/type/required). Use this to find tool IDs, then call
execute_operation with the chosen operation_name and params. No execution happens here.
execute_operationA
Execute one API operation by name. Use operation_name from discover_operations;
provide path_params, query_params, and optionally body_data as required by the schema.
Returns the API response body or an error string.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: discover_operations is for discovery only, while execute_operation is for execution. There is no overlap, and the dependency between them is explicit and unambiguous.

Naming Consistency5/5

Both tool names follow the consistent verb_noun pattern: 'discover_operations' and 'execute_operation'. The naming is clean, predictable, and uses the same style throughout.

Tool Count4/5

The server has only two tools, which is slightly below the typical 3-15 range, but it is justified by the narrow scope of the server: discovering and executing operations. Each tool is essential and the pair is sufficient for the stated purpose.

Completeness5/5

For a generic API executor, the two-step lifecycle of discover then execute is fully covered. The discover tool provides enough information (operation name, method, URL, parameters) to call execute_operation without any obvious gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources