Skip to main content
Glama
AlanRoybal

prompte-mcp

by AlanRoybal
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

get_config

Retrieve the current configuration settings from the ~/.prompte/config.json file to access prompt enhancement preferences and optimization parameters.

Instructions

Read the current ~/.prompte/config.json

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • bin/prompte-mcp.js:211-213 (handler)
    The 'get_config' tool handler inside the MCP server's dispatch function.
    case 'get_config': {
  return getConfig();
}
  • src/config/profile.js:43-46 (helper)
    The core implementation that reads and returns the configuration JSON.
    export function getConfig() {
  const stored = readJSON(CONFIG_FILE);
  return { ...DEFAULT_CONFIG, ...stored };
}

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

Annotations are absent so description carries full burden. 'Read' correctly implies non-destructive file access, and the specific path discloses scope. However, lacks details on error behavior (file missing), return format structure, or whether content is parsed or raw.

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?

Perfectly concise. Front-loaded imperative verb, zero redundancy. Every word earns its place in describing the operation and target file.

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

Completeness3/5

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

Adequate but incomplete for a data retrieval tool with no output schema or annotations. While the file path provides context, missing description of return value structure (parsed JSON vs string) or error cases leaves gaps.

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?

Zero parameters present, establishing baseline of 4. Description compensates appropriately by specifying the implicit target resource (config file path), adding context beyond the empty schema.

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?

Excellent clarity. Specific verb 'Read' + exact resource path '~/.prompte/config.json'. Clearly distinguishes from sibling 'set_config' (implied write operation) and other tools like 'get_stats' or 'list_techniques'.

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?

No explicit guidance on when to use vs alternatives. Lacks mention of sibling 'set_config' for modification scenarios or prerequisites like file existence. Agent must infer usage from verb alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlanRoybal/prompte-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server