Skip to main content
Glama

get_project

Reads a VOCALOID3–6 project file and returns its tempo, time signatures, tracks, parts, singers, and curves for inspection.

Instructions

Tempo, time signatures, tracks, parts, singers, curves. / テンポ・拍子・トラック・パート・歌手・カーブの概要

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It identifies some content categories but does not explain read-only behavior, permissions, errors, default path handling, or return format.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bilingual noun-list format is brief and front-loaded, but it is a fragment rather than a well-formed tool description. It avoids waste but sacrifices clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should explain both return contents and the optional path parameter. It lists some content categories but leaves return shape and path behavior undefined.

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

Parameters1/5

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

The single optional path parameter has 0% schema description coverage and is never mentioned in the description. The description does nothing to compensate for that missing parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name get_project and the Japanese word 概要 indicate a project overview, while the English text lists data categories. However, the English description has no verb and never explicitly says it retrieves a project summary, so the exact purpose must be inferred from the name.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no routing to related tools such as get_curve or get_voicebank. The only implied usage is retrieving a project overview.

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