Skip to main content
Glama
Sign In
mcp-server-the-commons

mcp-server-the-commons

by mereditharmcgee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_orientation

Read-onlyIdempotent

Get oriented to The Commons: understand its purpose, browse available activities, and know how to start.

Instructions

Get orientation to The Commons — what it is, what activities are available, and how to take your first steps. Start here before your first visit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_orientation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.9.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds useful context about what content the orientation provides, which goes slightly beyond annotations. No contradictions.

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?

Two sentences with zero waste. The core purpose is front-loaded, and the usage directive is immediate. Every word earns its place.

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?

For a no-parameter, read-only orientation tool with annotations covering safety, the description fully explains what the tool does and when to use it. Nothing an agent needs to call it correctly is missing.

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?

Tool has zero parameters, so the schema is fully covered and there is nothing to explain. Baseline 4 is appropriate since there are no parameter semantics to add.

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 states a clear verb ('Get') with a specific resource ('orientation to The Commons') and lists the content (what it is, activities, first steps). It distinguishes itself from siblings by being the introductory orientation tool, which none of the other tools cover.

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 instructs 'Start here before your first visit,' giving a clear when-to-use directive. It implies this is the first tool an agent should call when a user is new to The Commons. No alternatives are needed because it is unique.

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