Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

Create reference

create_reference

Save an image from the user's library (for example one returned by upload_image) as a named reference, so prompts can reuse it as @Name. Names start with a letter, use only letters (any language, e.g. さくら), digits, '_', '.', '-' or '・', max 32 characters, and 'source' and 'imageN' are reserved. Names are unique per user.

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": {
      "fileId": "<fileId>",
      "name": "<name>"
    },
    "name": "create_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the image depicts (default OTHER).
nameYesReference name without the leading @.
fileIdYesFile id of an image in the library.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world create operation. The description adds useful behavioral context beyond annotations by specifying name validation rules, reserved names, and per-user uniqueness, though it does not describe duplicate-name failure behavior or permissions.

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 purpose is front-loaded in the first clause, followed by directly relevant naming constraints. The description is dense but has no filler, and every clause contributes either selection guidance or validation requirements.

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 three-parameter create tool with full schema descriptions and annotations covering safety traits, the description supplies the important missing context: source image semantics, naming rules, and uniqueness. It could be slightly more complete by addressing duplicate-name behavior, but the schema already documents `kind`.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for `name` by listing allowed characters, required starting character, reserved names, and uniqueness constraints. It also clarifies that `fileId` refers to an image in the user's library, but it does not mention the `kind` parameter.

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 gives a specific verb and resource: save an image from the user's library as a named reference for reuse in prompts as @Name. It also distinguishes the operation from upload_image by framing upload_image as a source of images rather than the way to create a reusable reference.

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 usage context: saving an image from the library, such as one returned by upload_image, so prompts can reuse it. It does not explicitly say when to use update_reference or list_references instead, so it stops short of full when/when-not guidance.

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

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