Skip to main content
Glama
Sign In
orquestra-core

orquestra-core

by internetdozero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

orquestra_append_mission_rule

Append a mission rule to a section of master AGENTS.md and create a backup to update agent instructions.

Instructions

Append a mission directive to a section of the master AGENTS.md, with a backup.

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": {
      "section_title": "<section_title>",
      "rule_content": "<rule_content>"
    },
    "name": "orquestra_append_mission_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_contentYes
section_titleYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 and does disclose key traits: it appends rather than overwrites, it targets the master AGENTS.md, and it takes a backup. It omits permissions, whether a missing section is created, and failure/concurrency behavior, so it is only partially adequate for a mutation tool.

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?

A single front-loaded sentence with no filler; the append action and the backup side effect appear immediately. It is efficient, though extremely brief.

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 values need not be explained, but with 0% parameter coverage and no annotations the description leaves real gaps: section-matching semantics, backup location, and whether the section is created if absent.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must compensate. 'A section' loosely maps to section_title and 'mission directive' to rule_content, but it gives no format, matching, or content-structure guidance for either parameter.

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?

States a specific verb (append), a specific resource (mission directive / rule) and its destination (a section of the master AGENTS.md), which is enough to distinguish it from siblings like create_skill or toggle_mcp. It doesn't explicitly name an alternative tool, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The agent must infer from the verb alone that this is for adding persistent project directives.

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