market-pulse

Get one directory resource

pulse_resource_detail

Read-onlyIdempotent

Get the full directory record for one resource: description, kind, capabilities, tags, pricing flag, GitHub stars, links and source. Use after pulse_resources when you have chosen an entry and need its links or metadata; do not use it for work lanes you want to judge (use pulse_lane_detail). Read-only and idempotent. Works without an API key on the free tier. Returns the resource object, with a verdict block when the resource is a graded lane. An unknown slug is refused with an error naming it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Resource slug exactly as returned in the slug field of pulse_resources.

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	Resource kind.
`name`	Yes	Display name.
`slug`	Yes	Resource slug.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / slug / description

Previous value: -"Resource slug as returned by pulse_resources."New value: +"Resource slug exactly as returned in the slug field of pulse_resources."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "kind": {
+      "description": "Resource kind.",
+      "type": "string"
+    },
+    "name": {
+      "description": "Display name.",
+      "type": "string"
+    },
+    "slug": {
+      "description": "Resource slug.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "kind"
+  ],
+  "type": "object"
+}

First observedSep 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description nonetheless adds real operational context: it works without an API key on the free tier, returns a verdict block for graded lanes, and refuses an unknown slug with an error naming it. Return-format detail is somewhat redundant with the output schema.

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?

Front-loads the purpose, then routing guidance, then behavioral facts, then return/error behavior. Efficient and well ordered, though the field enumeration and return details are slightly dense for a one-parameter lookup.

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?

For a single-slug read tool with full annotations and an output schema, the description covers purpose, routing, auth tier, error behavior, and the odd verdict-block return. Nothing needed to call it correctly is missing.

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 there is a single parameter, so the schema fully documents the slug and its exact format. The description adds no syntax or constraint beyond 'one resource', so the 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?

States a specific verb (Get) and resource (full directory record for one resource) and enumerates the returned fields (description, kind, capabilities, tags, pricing flag, stars, links, source). It explicitly distinguishes itself from pulse_resources and pulse_lane_detail, so an agent can route without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use after pulse_resources when you have chosen an entry and need its links or metadata') and an explicit exclusion with the named alternative ('do not use it for work lanes you want to judge (use pulse_lane_detail)'). Both when-to-use and when-not-to-use are covered.

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

All market-pulse tools Inspect

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.