Skip to main content
Glama

generate_test_skeleton

Generate a C# test-class skeleton for a method or type, returning full file contents with test stubs, assertions, and todo notes for wiring up dependencies.

Instructions

Emits a test-class skeleton (parseable C#) for a method or type. Pass a type FQN like 'MyApp.Services.OrderService' to get a full test class with one stub per public method, or a method FQN like 'MyApp.Services.OrderService.PlaceOrder' to get a single stub. Returns framework, suggested file path, class name, full file contents (as text), and TodoNotes for things to wire up (e.g. constructor dependencies). The tool does NOT write to disk — agent decides what to do with the text. Pairs naturally with find_uncovered_symbols / get_test_summary. Stubs include happy-path Fact, Theory + InlineData for primitive-param methods, and Assert.Throws assertions per distinct direct-throw exception type. Async (Task-returning) methods detected automatically. Properties, indexers, operators, and constructors are excluded from per-method enumeration. Framework auto-detected from solution test projects (tie → xUnit); override with framework='xunit' / 'nunit' / 'mstest'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesFQN of a type or method to generate a test skeleton for.
frameworkNoOptional framework override: 'xunit', 'nunit', or 'mstest'. Auto-detected if null.
Behavior5/5

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

With no annotations, the description carries full burden. It fully discloses that the tool does not write to disk, what stubs include (happy-path Fact, Theory+InlineData, Assert.Throws), async detection, framework auto-detection, and returns TodoNotes. There are no hidden behaviors or contradictions.

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?

The description is a single dense paragraph that front-loads the main purpose. Every sentence contributes useful information, but it could be more scannable with bullet points. It is efficient but slightly verbose for an AI agent's quick parsing.

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?

Despite no output schema, the description fully explains the return content (framework, file path, class name, file contents, TodoNotes). It covers edge cases like async detection, framework override, and exclusion of properties/operators. The tool's behavior is completely specified for an agent to use correctly.

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?

Schema coverage is 100%, but the description adds value beyond the schema by explaining how the symbol FQN works (type vs method) and providing example usage. For the framework parameter, it lists the allowed values and explains auto-detection. This enhances understanding beyond the schema's property descriptions.

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 clearly states it emits a test-class skeleton (parseable C#) for a method or type. It distinguishes from siblings by mentioning pairing with find_uncovered_symbols and get_test_summary. The verb 'emits' and the specific output (framework, file path, class name, file contents, TodoNotes) make the purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool (generating test stubs) and what it does not do (not write to disk). It specifies exclusions (properties, indexers, operators, constructors) and mentions options to override framework. However, it does not explicitly contrast with alternatives like 'find_uncovered_symbols' or 'get_test_summary', though it pairs with them.

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/MarcelRoozekrans/roslyn-codelens-mcp'

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