Skip to main content
Glama
Sign In
mcp-artisan

mcp-artisan

by 0mandrock1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

project_summary

Count key Laravel project elements and fetch version numbers in a single call to quickly orient yourself in the codebase.

Instructions

Counts and versions for cheap orientation, in one call.

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": "project_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior1/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 does not explain what is counted, what versions refer to, whether the call is read-only, or what the response structure looks like. 'Cheap orientation' hints at low cost but is not a concrete behavioral trait.

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 sentence with no redundant words. It is front-loaded with the core action ('Counts and versions') and efficient. However, its brevity contributes to under-specification, but that is penalized in other dimensions, not here.

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

Completeness1/5

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

Given there are no annotations and no output schema, the description is the sole source of context. It fails to specify what counts are provided, what versions are reported, or the format of the result. This is inadequate for an agent to reliably select and invoke the tool, especially when siblings offer more explicit functionality.

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?

The tool has zero parameters, and the schema coverage is 100% (empty schema). Per the baseline for parameterless tools, the description does not need to explain parameters, and it does not undermine the schema. No additional parameter semantics are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Counts and versions for cheap orientation,' which indicates the tool provides aggregated counts and version information for a quick overview. However, it does not specify which resources are counted or whose versions are returned, making the purpose somewhat vague compared to the more specific sibling tools.

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 usage guidance is provided. The description implies using this for 'cheap orientation' but does not state when to choose this tool over siblings like list_routes or list_models, nor does it mention any exclusions or prerequisites.

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