FD Solutions MCP Server

Overview Schema Source Related Servers Discussions Admin

Set source signal

set_source_signal

Assign a custom time-domain signal to an existing FDTD/FDFD source by providing time, amplitude, and phase vectors for pulses such as modulated Gaussian or multi-peak waveforms.

Instructions

Assign a user-defined time-domain signal to an existing source (setsourcesignal).

Used in FDTD / FDFD for custom pulses (modulated Gaussian, multi-peak, etc.). This is not set_property — ordinary wavelength / pulse settings still use set_property on the selected source.

t, amplitude, and phase must be equal-length 1D vectors (SI: s, —, rad). Prefer starting t at 0 so the initial field is zero.

Input Schema

Name	Required	Description
`t`	Yes	Time samples in seconds (SI), same length as amplitude and phase.
`phase`	Yes	Phase samples (radians), same length as t.
`fcentre`	No	Optional center frequency in Hz (SI). If set with bandwidth, used for material fits, mesh, and source limits; otherwise estimated from the signal.
`amplitude`	Yes	Amplitude envelope samples, same length as t.
`bandwidth`	No	Optional bandwidth in Hz (SI). Use together with fcentre.
`source_name`	Yes	Existing source path, e.g. 'FDTD::plane'. Does not create a source — add + optionally rename first.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4.2/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 behavioral burden. It helpfully states that the source must already exist, that the vectors must be equal length, and that `t` should preferably start at 0, but it does not explicitly describe overwrite behavior, reversibility, or other side effects of assigning a new signal.

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 short, front-loaded, and every sentence contributes: purpose, context, sibling differentiation, vector constraints, units, and a practical default. No sentence is redundant.

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

Completeness4/5

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

Given the rich schema and presence of an output schema, the description covers the essential calling context: existing source requirement, vector-length constraint, units, and alternative tool routing. The main remaining gap is explicit mutation/overwrite behavior, which is not covered by annotations.

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 already 100%, so the schema fully documents parameter meanings and units. The description reinforces the equal-length constraint and adds practical guidance to start `t` at 0, but it does not add substantial meaning beyond the schema for the optional `fcentre` and `bandwidth` parameters.

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 specific verb and resource: assign a user-defined time-domain signal to an existing source. It immediately distinguishes the operation from `set_property`, making the tool's role clear against a key sibling.

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?

It explicitly says the tool is for custom pulses in FDTD/FDFD and clarifies that ordinary wavelength or pulse settings should still use `set_property`. This gives a clear when-to-use and when-not-to-use boundary with an alternative named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.