Skip to main content
Glama

get_service

Retrieve detailed information for any service on the402.ai marketplace by its ID, including pricing, required inputs, deliverables, estimated delivery time, provider details, and reputation scores.

Instructions

Get full details for a specific service on the402.ai by its ID. Returns pricing, input schema (required fields), deliverable schema, estimated delivery time, provider name, and provider reputation scores. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_idYesThe service ID to look up

Implementation Reference

  • Registration and implementation of the 'get_service' tool.
    server.tool(
    	"get_service",
    	"Get full details for a specific service on the402.ai by its ID. Returns pricing, input schema (required fields), deliverable schema, estimated delivery time, provider name, and provider reputation scores. No authentication required.",
    	{
    		service_id: z.string().describe("The service ID to look up"),
    	},
    	async ({ service_id }) => {
    		const result = await client.get(`/v1/services/${service_id}`);
    		return {
    			content: [
    				{ type: "text" as const, text: JSON.stringify(result, null, 2) },
    			],
    		};
    	}
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: it's a read operation ('Get'), specifies the return data structure (pricing, input schema, etc.), and explicitly states 'No authentication required'. However, it doesn't mention potential errors, rate limits, or response format details, leaving some behavioral aspects uncovered.

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?

The description is front-loaded with the core purpose in the first sentence, followed by specific return details and authentication note. Every sentence earns its place by adding critical information without redundancy, making it efficient and well-structured.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is largely complete: it covers purpose, return data, and authentication. However, without an output schema, it could benefit from more detail on response structure or error handling, but it's sufficient for basic use.

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 the schema already documents the single parameter 'service_id'. The description adds no additional meaning beyond what's in the schema (e.g., format examples or ID sourcing). With high schema coverage, the baseline is 3, and the description doesn't compensate with extra parameter insights.

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?

The description clearly states the verb 'Get' and resource 'full details for a specific service on the402.ai by its ID', distinguishing it from siblings like browse_products or search_catalog. It specifies the exact scope of information returned (pricing, input schema, deliverable schema, etc.), making the purpose unambiguous.

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?

The description implies usage by stating 'by its ID' and 'No authentication required', but does not explicitly say when to use this tool versus alternatives like inquire_service or get_platform_info. It provides basic context but lacks explicit guidance on when-not-to-use or direct comparisons with sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/the402ai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server