Skip to main content
Glama

get_prompts

View global prompt settings for task management, including instructions, prefixes, and suffixes applied to all tasks in TaskFlow MCP.

Instructions

Get the current prompts configuration including instructions, taskPrefix, and taskSuffix settings.

This tool helps you view the current global prompts settings that are applied to all tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_prompts' tool, which calls the service method to retrieve prompts.
    async get_prompts() {
      return service.getPrompts();
    },
  • Tool schema definition including name, description, and empty input schema for 'get_prompts'.
    export const GET_PROMPTS_TOOL: Tool = {
      name: "get_prompts",
      description:
        "Get the current prompts configuration including instructions, taskPrefix, and taskSuffix settings.\n\n" +
        "This tool helps you view the current global prompts settings that are applied to all tasks.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • Registration of the 'get_prompts' tool (as GET_PROMPTS_TOOL) in the server's listTools handler.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        PLAN_TASK_TOOL,
        GET_NEXT_TASK_TOOL,
        MARK_TASK_DONE_TOOL,
        OPEN_TASK_DETAILS_TOOL,
        LIST_REQUESTS_TOOL,
        ADD_TASKS_TO_REQUEST_TOOL,
        UPDATE_TASK_TOOL,
        DELETE_TASK_TOOL,
        ADD_SUBTASKS_TOOL,
        MARK_SUBTASK_DONE_TOOL,
        UPDATE_SUBTASK_TOOL,
        DELETE_SUBTASK_TOOL,
        EXPORT_TASK_STATUS_TOOL,
        ADD_NOTE_TOOL,
        UPDATE_NOTE_TOOL,
        DELETE_NOTE_TOOL,
        ADD_DEPENDENCY_TOOL,
        GET_PROMPTS_TOOL,
        SET_PROMPTS_TOOL,
        UPDATE_PROMPTS_TOOL,
        REMOVE_PROMPTS_TOOL,
        ARCHIVE_COMPLETED_REQUESTS_TOOL,
        LIST_ARCHIVED_REQUESTS_TOOL,
        RESTORE_ARCHIVED_REQUEST_TOOL,
      ],
  • The service method implementing the core logic: loads task data and returns the prompts configuration.
    public async getPrompts() {
      await this.loadTasks();
      return {
        status: "prompts_retrieved",
        prompts: this.data.prompts || null,
        message: this.data.prompts ? "Current prompts configuration retrieved." : "No prompts configuration found."
      };
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that this is a read operation ('Get', 'view') and specifies the scope ('global prompts settings applied to all tasks'), which is useful behavioral context. However, it lacks details on permissions, rate limits, or response format, leaving gaps for a tool with no annotation coverage.

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 description is front-loaded and efficient: the first sentence clearly states the purpose and key fields, and the second sentence adds useful context about global application. Both sentences earn their place without redundancy or fluff, making it appropriately sized for a simple tool.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is reasonably complete for basic understanding. It explains what the tool retrieves and its scope. However, without annotations or output schema, it could benefit from more detail on return format or error conditions, leaving some contextual 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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and output semantics (e.g., 'including instructions, taskPrefix, and taskSuffix settings'), adding value beyond the empty schema. Baseline for 0 parameters is 4.

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?

The description clearly states the tool's purpose: 'Get the current prompts configuration' with specific fields (instructions, taskPrefix, taskSuffix). It distinguishes from siblings like 'set_prompts' and 'update_prompts' by focusing on retrieval rather than modification. However, it doesn't explicitly contrast with 'remove_prompts' or other prompt-related tools.

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 description implies usage context by stating it 'helps you view the current global prompts settings that are applied to all tasks,' suggesting it's for configuration inspection. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'set_prompts' or 'update_prompts,' nor does it mention prerequisites or exclusions.

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/pinkpixel-dev/taskflow-mcp'

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