Skip to main content
Glama
Sign In
evc-spark-mcp

evc-spark-mcp

by entire-vc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_asset_content

Retrieve raw content of a Spark asset: prompt text, skill instructions, or agent config. Ideal for accessing inline content of prompts and skills.

Instructions

Get the raw content of a Spark asset (prompt text, skill instructions, agent config). Best for prompts and skills that have inline content.

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": {
      "slug": "<slug>"
    },
    "name": "get_asset_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesAsset slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the core behavior (getting raw content) but does not address error handling, permissions, or response format. Adequate for a simple read operation but minimal.

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?

Two sentences, front-loaded with action ('Get the raw content'), no redundant information. Efficient and direct.

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?

For a single-parameter tool with no output schema, the description explains purpose and provides usage guidance. It could mention return format but is largely complete for its simplicity.

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% with one parameter 'slug' described as 'Asset slug'. Description adds context about asset types but does not enhance parameter understanding beyond schema. Baseline score 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 states verb 'Get', resource 'raw content of a Spark asset', and provides examples (prompt text, skill instructions, agent config). It implicitly distinguishes from sibling 'get_asset' which likely retrieves metadata.

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?

Description says 'Best for prompts and skills that have inline content', which implies usage context but does not explicitly state when not to use it or name alternative tools. Lacks explicit exclusions.

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