Skip to main content
Glama
Sign In

Krusgraph

by com.krusgraph
OverviewDiscussions(1)Admin

Starter pack for an app on a GraphQL API

app_starter
Read-only

Generates a starter pack for an app on an API for GraphQL item: a Lovable prompt, connection details, five GraphQL queries that follow the relationships, a Supabase edge function and the portal steps left. Requires workspace and an API that create_backend has created. Returns JSON {lovable_prompt, connection, queries, checklist, backend, note}. Changes nothing; app_readiness lists what the API lacks. Errors: {error, kind, hint}.

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": {
      "workspace": "<workspace>",
      "api": "<api>"
    },
    "name": "app_starter"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiYesAPI for GraphQL item created by create_backend, by name or id.
workspaceYesFabric workspace, name or id.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / api / description
      Added value: +"API for GraphQL item created by create_backend, by name or id."
    • addedInput schema / properties / workspace / description
      Added value: +"Fabric workspace, name or id."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description corroborates them with "Changes nothing" while adding value beyond them: the shape of the returned JSON and the error contract {error, kind, hint}. The openWorldHint=true dependency on a live API is implied by the create_backend prerequisite rather than spelled out, which keeps it from a 5.

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?

The opening sentence front-loads the purpose and the deliverables, and the trailing sentences carry prerequisite, return shape, safety, and error format with no filler. The brace-list of JSON keys is dense but earns its place; only minor trimming would improve flow.

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?

With an output schema present, annotations covering the safety profile, and 100% schema coverage, the description still supplies the two things structured fields cannot: the create_backend prerequisite and the error object shape. Nothing an agent needs to invoke this 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 description coverage is 100%, so both parameters (workspace, api) are already fully documented in the schema, including that api accepts a name or id. The description reinforces the provenance of the api parameter (must come from create_backend) but adds no syntax or format detail beyond the schema; 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?

The description uses a specific verb ("Generates a starter pack") on a specific resource (an app on a GraphQL API item) and then enumerates the exact artifacts produced: Lovable prompt, connection details, five relationship-following queries, a Supabase edge function, and remaining portal steps. That level of detail distinguishes it from siblings like app_readiness or query_graphql without opening either schema.

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

Usage Guidelines4/5

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

It states a clear precondition ("Requires workspace and an API that create_backend has created") and routes the agent elsewhere for a related need ("app_readiness lists what the API lacks"). It never gives an explicit when-not-to-use or a full alternative-selection rule, so it falls short of a 5, but the context is unambiguous.

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

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