Skip to main content
Glama

list_profiles

Lists available platform profiles, rule versions, prompt dimensions, and foreshadowing number prefixes to configure constraint-driven novel-writing and review pipelines.

Instructions

列出可用平台档案、规则版本、提示词维度与伏笔编号前缀(对齐 novel-review-mcp 的 list_profiles)。

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": "list_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does identify the four content categories returned. For a zero-parameter, zero-side-effect local listing that is close to sufficient, but it says nothing about the response shape or whether values are static config versus project-derived.

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?

A single front-loaded sentence with the verb first and the four returned categories enumerated compactly. The trailing parenthetical about alignment with novel-review-mcp ("对齐 novel-review-mcp 的 list_profiles") is provenance metadata of marginal use to a calling agent and is the one element that does not fully earn its place.

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?

With no annotations and no output schema, the description must convey what comes back, and it does so at the category level for all four groups. Given the trivial zero-param surface, this is nearly complete; only the concrete response keys are left unspecified.

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?

The tool takes no parameters (schema is an empty object), so there is nothing for the description to disambiguate; the baseline for a zero-param tool applies. The description adds no parameter meaning because none exists to add.

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?

"列出" supplies a concrete verb and the object is enumerated precisely: platform profiles, rule versions, prompt dimensions, and foreshadow ID prefixes ("平台档案、规则版本、提示词维度与伏笔编号前缀"). An agent can tell this is a read-only discovery/enumeration tool rather than one of the check_*/extract_* siblings. It stops short of 5 because nothing explicitly distinguishes it from a sibling like foreshadow_list, which could plausibly overlap on the prefix information.

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?

The word "可用" (available) implies the tool is meant to enumerate valid values before other calls, but there is no explicit statement of when to call it, what it precedes, or what it does not cover. Usage is only inferable from the discovery nature of the tool, not stated.

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