Skip to main content
Glama
Sign In

mcp

by xyz.dreamtap
OverviewDiscussionsAdmin

get_inspirations

Get sources of inspiration. Always use this when working on creative tasks - call this tool before anything else.

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": {
      "level": "<level>"
    },
    "name": "get_inspirations"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesthe amount of inspiration you need, use low for simple tasks and high for very creative tasks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the tool's purpose and usage, but does not mention any behavioral traits such as side effects, return format, or whether it is read-only. This leaves the agent with minimal information about what to expect after invocation.

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 concise, consisting of two sentences that efficiently convey purpose and usage. It is front-loaded with the core function and immediately provides actionable guidance. No wasted words.

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 simplicity (one parameter, no output schema, no siblings), the description covers the essential context: what it does and when to use it. It does not describe return values, but for a 'get inspirations' tool, this is not critical. The guidance to 'call before anything else' adds important workflow context.

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?

The input schema covers 100% of parameters, including a description for 'level' that explains its meaning and usage. The tool description does not add further parameter details beyond the schema, but since the schema is already self-explanatory, a baseline score of 3 is appropriate.

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 states the tool's function as 'Get sources of inspiration,' which is a specific verb and resource, making its core purpose clear. Without sibling tools to differentiate from, this level of specificity is sufficient. It could be slightly more descriptive but is not vague or tautological.

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?

The description explicitly instructs when to use the tool: 'Always use this when working on creative tasks - call this tool before anything else.' This provides clear context and ordering guidance, effectively telling the agent the tool is a prerequisite for creative workflows. No alternatives are needed since there are no sibling tools.

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

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