Skip to main content
Glama
kapillamba4

meta-prompt-mcp

by kapillamba4
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_google_guide

Retrieves Google's official Prompting Guide to help write, refine, or optimize prompts. Use it when you need to craft high-quality prompts following proven best practices.

Instructions

USE THIS TOOL proactively when you need to write, create, refine, or optimize any prompt. Retrieves Google's official Prompting Guide as reference material to help you generate higher-quality prompts.

ALWAYS CALL THIS TOOL when:

  • You are tasked with writing a prompt (for yourself or another system)

  • You need to refine or improve an existing prompt

  • You are designing system prompts, few-shot examples, or chain-of-thought structures

  • The user asks you to "write a prompt for..." or "help me craft a prompt"

Do NOT wait for explicit permission — call this tool at the start of any prompt-writing task to ensure your output follows proven best practices.

Returns: The complete Google Prompting Guide markdown content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations provided; description clearly states it retrieves guide content and returns markdown. Could mention read-only nature explicitly but sufficient.

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?

Well-structured with bold headings and bullet points. Front-loaded with imperative. Slightly verbose but effective.

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

Completeness5/5

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

Completely covers purpose, usage, and return type for a zero-parameter tool with output schema present.

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?

No parameters, baseline of 4. No additional parameter info needed.

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?

Clearly states the tool retrieves Google's official Prompting Guide for prompt writing. Distinguishes from sibling get_anthropic_guide by name and content.

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

Usage Guidelines5/5

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

Explicitly lists when to use (writing, refining prompts) and includes imperative 'ALWAYS CALL' and 'do not wait for explicit permission'.

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/kapillamba4/meta-prompt-mcp'

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