Skip to main content
Glama
Sign In
agentstorefront-mcp

agentstorefront-mcp

by lmaniraruta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_service

Retrieve full details of a single AgentStorefront service including schema, pricing, rate limits, SLA, and sample inputs/outputs.

Instructions

Get full details on a single AgentStorefront service: schema, pricing, rate limits, SLA, sample inputs/outputs.

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": {
      "service_id": "<service_id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_idYesThe service ID (UUID or slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It explains what the tool returns (schema, pricing, etc.) and implies a read-only operation by using 'Get'. More detail on auth or rate limits would raise score, but current disclosure is adequate for a simple retrieval tool.

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?

Single sentence, front-loaded with action and object, includes specific data details. No wasted words.

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

Completeness5/5

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

Tool has one simple parameter, no output schema, but description enumerates return fields (schema, pricing, etc.) sufficiently. All necessary context for an agent to invoke correctly.

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?

Only one parameter 'service_id' with schema description already clear ('UUID or slug'). Description adds no extra meaning beyond what the schema provides, so baseline 3 applies.

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?

Description specifies 'Get full details on a single AgentStorefront service' and lists specific data fields (schema, pricing, rate limits, etc.). It clearly distinguishes from siblings list_services and search_services, which are for listing and searching, and request_quote, which is for quoting.

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 by contrasting with siblings (list_services and search_services for broader retrieval, request_quote for quoting). However, no explicit when-to-use or when-not-to-use statements are provided.

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

Deploy Server

Other Tools