Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Update Focus Overview

update_focus_overview

Replaces a focus area's standing overview using its slug and new Markdown, so you can revise the 'what matters here' narrative that orients you whenever you return to the subject.

Instructions

Replace a focus area's standing overview — the "what matters here" narrative.

This is the piece that was going to be the AI course's introduction: the
orientation you want in front of you every time you open the subject, as
opposed to the feed, which changes daily.

Args:
    slug: The focus slug.
    overview: Markdown. Replaces the existing overview entirely.

Returns:
    Confirmation and the new length.

Input Schema

NameRequiredDescriptionDefault
slugYes
overviewYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most important trait: the existing overview is replaced entirely, making this a destructive overwrite. It also states the return value (confirmation plus new length). It does not say whether the prior overview is recoverable or what happens if the slug doesn't exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core statement is correctly front-loaded, but the middle paragraph about the "AI course's introduction" is anecdotal filler that delays the concrete Args section. The Args/Returns block is useful but the framing prose could be cut to one clause.

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?

An output schema exists, so return details are already covered. Still missing for a mutation tool with no annotations: whether a missing slug errors or creates, whether the overwrite can be undone, and how to resolve a slug to a focus area.

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 0%, so the description must compensate, and it partially does by clarifying that overview is Markdown and is a full replacement. However slug is only restated as "the focus slug" with no format or how to discover it, leaving the lookup path undocumented in both schema and description.

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?

First line gives a precise verb+resource: "Replace a focus area's standing overview." It also draws a conceptual boundary against the daily feed, which is the main adjacent resource in this tool family. It stops short of naming specific siblings like focus_brief or show_focus_areas.

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 (this is the durable orientation text, not the changing feed) but never states when to call this instead of focus_brief, create_focus_area, or set_focus_state. An agent has to infer the selection criteria from the metaphor rather than from explicit guidance.

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