Skip to main content
Glama
ampcome-mcps

Shortcut MCP Server

by ampcome-mcps

get-objective

Retrieve a Shortcut objective using its public ID to access project details and track progress within the MCP server.

Instructions

Get a Shortcut objective by public ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectivePublicIdYesThe public ID of the objective to get

Implementation Reference

  • Handler function that fetches the Shortcut objective (milestone) by public ID using the client, handles errors, and formats the result using base tool methods.
    async getObjective(objectivePublicId: number) {
    	const objective = await this.client.getMilestone(objectivePublicId);
    
    	if (!objective)
    		throw new Error(`Failed to retrieve Shortcut objective with public ID: ${objectivePublicId}`);
    
    	return this.toResult(
    		`Objective: ${objectivePublicId}`,
    		await this.entityWithRelatedEntities(objective, "objective"),
    	);
    }
  • Zod input schema defining the 'objectivePublicId' parameter for the get-objective tool.
    {
    	objectivePublicId: z.number().positive().describe("The public ID of the objective to get"),
    },
  • Registers the 'get-objective' tool with the MCP server, specifying name, description, input schema, and delegating to the getObjective handler.
    server.tool(
    	"get-objective",
    	"Get a Shortcut objective by public ID",
    	{
    		objectivePublicId: z.number().positive().describe("The public ID of the objective to get"),
    	},
    	async ({ objectivePublicId }) => await tools.getObjective(objectivePublicId),
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a read operation ('Get'), but doesn't cover permissions, error handling, rate limits, or response format. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to understanding the tool's purpose.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a retrieval tool. It doesn't explain what an 'objective' is in this context, what data is returned, or any behavioral aspects like authentication needs. For a tool with one parameter but missing structured context, it should provide more guidance.

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 100%, with the single parameter 'objectivePublicId' fully documented in the schema. The description adds minimal value by mentioning 'by public ID', which aligns with the schema but doesn't provide additional context like format examples or constraints beyond what's in the schema. Baseline 3 is appropriate given high schema coverage.

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?

The description clearly states the action ('Get') and resource ('a Shortcut objective'), specifying it's by 'public ID'. It distinguishes from siblings like 'search-objectives' by focusing on retrieval of a specific item rather than searching. However, it doesn't explicitly contrast with other 'get-' tools (e.g., 'get-story'), leaving some ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose this over 'search-objectives' or other retrieval tools like 'get-story', nor does it specify prerequisites or exclusions. Usage is implied by the name but not explicitly stated.

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/ampcome-mcps/shortcut-mcp'

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