Skip to main content
Glama
Sign In
geo-figure-mcp

geo-figure-mcp

by skyblue3925-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

make_figures

Generate editable black-and-white geography exam figures—maps, terrain diagrams, and data charts—as PPTX or HWPX files from a figure spec, after confirming the plan summary with the teacher.

Instructions

그림 명세로 PPTX·HWPX 파일을 만든다. 만들기 전에 교사에게 계획 요약을 보여 주고 확인을 받았는지 먼저 확인한다. 명세 작성법은 guide.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "figures": "<figures>",
      "confirmed": "<confirmed>"
    },
    "name": "make_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo파일 이름(확장자 제외)지리자료
styleNo이번 파일에만 쓸 글꼴·크기(학교 양식)
outDirNo저장 폴더(기본 /root/Documents/지리시험자료)
figuresYes그림 명세 목록 — guide 의 [그림 명세] 참고
formatsNo
answerKeyNo정답표 — 파일 마지막 장에 들어간다. 첫 줄은 제목
confirmedYes교사가 계획 요약을 보고 "예"라고 했으면 true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses an important behavioral gate (do not generate until teacher confirmation is obtained) and that files are produced in PPTX/HWPX. It does not cover overwrite behavior, whether existing files in outDir are replaced, or what the tool returns (file paths), which leaves meaningful gaps for a file-mutating tool.

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?

Three short sentences with zero filler, front-loaded with the action, followed by the precondition and the pointer to the guide. Every sentence earns its place.

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?

The tool is complex (nested figure objects, 7 params, file output) and has no output schema, so the description should ideally say what comes back (file paths, success/failure). It covers the action, formats, and confirmation prerequisite but leaves the return behavior unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 86%, so the schema already documents most parameters. The description adds the meaning of the 'confirmed' gate and points 'figures' to the guide's [그림 명세] section, but adds no detail on 'formats', 'style', or how 'answerKey' is rendered beyond the schema text. Baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: '그림 명세로 PPTX·HWPX 파일을 만든다' (creates PPTX/HWPX files from a figure specification). It also names the output formats and points to the 'guide' sibling for spec authoring, so an agent can tell what this tool produces and where the input format is documented.

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

Usage Guidelines4/5

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

It states a clear precondition — verify that a plan summary was shown to the teacher and confirmed before generating. It routes spec-writing questions to 'guide'. It stops short of stating when not to use the tool or what to do if confirmation is absent, so it stops short of a 5.

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

Deploy Server

Other Tools