Skip to main content
Glama
h-yanagawa

Research MCP Server

by h-yanagawa
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

get_survey_summary

Extract survey summaries from Notion pages to review collected data and analyze responses for research purposes.

Instructions

Get survey summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes

Implementation Reference

  • server.py:72-83 (handler)
    The handler function for the 'get_survey_summary' tool, registered via @mcp.tool(). It fetches the Notion page details, including properties and the plain text from the first code block, and returns them as a JSON string.
    @mcp.tool()
def get_survey_summary(page_id: str):
    """Get survey summary"""
    page = notion.pages.retrieve(page_id)
    parent = notion.blocks.retrieve(page_id)
    children = notion.blocks.children.list(page_id)
    body = ""
    for child in children["results"]:
        if child["type"] == "code":
            body = child["code"]["rich_text"][0]["plain_text"]
            break
    return json.dumps({"parent": parent, "properties": page["properties"], "body": body}, ensure_ascii=False)

Tool Definition Quality

D1.3/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers nothing beyond the basic action. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it has side effects, rate limits, or what format the summary returns. The description fails to compensate for the complete lack of 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.

Conciseness2/5

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

While technically concise with just three words, this description is under-specified rather than efficiently structured. It lacks the necessary information density - every word should earn its place, but these three words provide almost no value beyond the tool name itself. The description is too brief to be helpful.

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

Completeness1/5

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

Given a single undocumented parameter, no annotations, no output schema, and multiple sibling tools, the description is completely inadequate. It doesn't explain what a 'survey summary' is, how it differs from other survey-related tools, what the parameter means, or what the tool returns. For a tool with this complexity and context, the description fails to provide essential information.

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 schema description coverage is 0%, meaning the single parameter 'page_id' has no documentation in the schema. The description provides no information about this parameter - not what it represents, what format it should have, where to obtain it, or how it affects the operation. The description fails completely to compensate for the schema's documentation gap.

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

Purpose2/5

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

The description 'Get survey summary' is a tautology that merely restates the tool name without adding any meaningful context. It doesn't specify what 'survey summary' entails, what resource it retrieves, or how it differs from sibling tools like 'get_survey_summaries' (plural). The description fails to provide the specific verb+resource clarity needed for effective tool selection.

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

Usage Guidelines1/5

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

The description provides absolutely no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, appropriate contexts, or distinctions from sibling tools like 'get_survey_summaries' or 'create_new_survey_summary'. The agent receives no help in determining when this specific tool should be invoked.

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/h-yanagawa/research-mcp-server'

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